Delay node show the delay date\history date in status

[FrankKoster]

Hi,
In a fulfillment workflow we build a delay of 14days. The delay end date is visible in the workflow variables Delay Date. This future date I like to show in the node status or in the next-step Milestone status.

Something like: Workflow is delayed until: ......

I havent found a way to have formulas in the status text other than available job/node variables ${..}. 

Is something like ${jobUserData_DelayDateTime)+14days possible in the Status Planned (Definite)?

Or is the Delay Node runtime data - History - Delay Date available as a ${}-value.

Second question, can we use date formatting in the status text? 

Something like:  TO_CHAR(SYSDATE+14, 'YYYY-MM-DD HH24:MI:SS')

[JamiePryer · Accepted solution]

Hey

i would have thought you can process the date/time value to be easier to read, but im not sure how.

also, this sound similar to the work Clive Morrish‌ documented around using "milestones" which may be easier/better?

see here: https://community.rsa.com/community/products/governance-and-lifecycle/exchange/recipes/blog/2019/12/... 

[AhmedNofal]

you can add the milestone right after the delay node and since you already have the delay end date as a WF variable, place the message you want to appear in the milestone node + the delay end date WF variable syntax to look like:

Workflow is delayed until: ${jobUserData_DelayDateTime)

in the "Completed" field of the Status section of the milestone node highlighted bellow (no need to typecast the value from date to char):

Around your second question, you cannot directly put date formatting logic/functions to the "Completed" Field within the milestone node. You will need an intermediate SQL select node to format your date as wished and put that formatted date either in the same WF variable (overwriting the DelayDateTime if this variable is created manually and not via system) or in a new WF variable, then putting that WF variable syntax inside the "Completed" field of the milestone node.

[IanStaines]

Frank Koster‌ did this answer your question(s)?

[IanStaines]

There were no further comments on this thread so I am marking it as assumed answered.