How do I call fn-formatDate()?

Probably the easiest for you is to create a component workflow to format the dates so you can use it multiple times in your workflow (or by other workflows).  Here’s an example one which is using RegEx to perform all the manipulation.  NB make sure to change your time zone to your correct time zone in the format date to string action.

Export key: PCBXz9RoyrDLZTePUqMFam5gxp5tVhmWZEnULRgg31sSK7nNn

Just in case you are not allow to/can’t import a workflow to NWC-G here are the instructions to replicate.

Create a start variable.  Datetime data type.  I called mine Date to format.  Here’s the workflow outline

Create two workflow variables both are text data types

First one I’ve called “Raw date”.  Second one make sure you have ticked the output box.  I called mine “Formatted date”.

Here’s the workflow outline

Format date to string:

Apply a RegEx

The log action just logs the raw and formatted dates.

Hope that helps.

Hi, Chris_Ben -

Thank you for the response.  But like I explained above (in the “addendum” to my initial post), I was already familiar with the “2-step regex” workaround, and I’m successfully using it.

It’s just “disappointing” that I NEED this workaround.  The “Format Date Time” action should really support custom formats out of the box :(

Moreover, it’s REALLY disappointing that NAC (and particularly NAC-G) seems to offer ZERO capabilities for implementing ANY custom functionality that doesn’t involve relying on external web services.  Which, for our customer, simply isn’t allowed (for very good reasons).

Yep.  That’s precisely the point of NAC-G that it is locked down so malicious code cannot be accidentally executed for the protection of all of the Government agencies that require that level of control.

One other option for you but it’s a much bigger conversation with the customer is to look at deploying Nintex K2 on-prem.  That option provides both security and complete customisation but as you already have a very feasible solution with either a component workflow (or using the formatdate+regex combo) then there would need to be other reasons to think about moving.

“Custom date” is just one example.  “Generate a random number” is another example (I believe I have a workaround for that, too).

There’s an infinite number of things that any given application might NEED to do that don’t happen to be supported by “out-of-the-box” functionality.  Hence the need for SOME kind of “custom functionality”.

It’s unfortunate that, although NAC forms allow some custom functionality (for example, via in-line functions and JS plugins), NAC workflows only allow Xtensions...which only work with external web services :(

BTW:
I know nothing about “Nintex-K2”.  I’ve focused exclusively on Nintex RPA (for on-prem automation) and “Nintex Automation Cloud” (nee “Nintex Workflow”) for “workflows”.  But who knows: perhaps “Nintex-K2” might solve a lot of the challenges we’ve been facing.

Thank you for the tip :)

Hi ​@paulsm4,

As this will be a component workflow, you can pass start variables to it. Is it possible for the system calling the workflow to pass an already formatted date?

Thank you, Simon,  But in this case, the workflow needs to generate the custom-formatted date itself.
the 2-step “Format date from String/use regex” is an acceptable workaround.