Firstly, I'm very glad to hear that my guide was useful for you.
No I am afraid that you can't use runtime values in a datetime field so you would need to use a calculation to insert it. There is a document which might be useful to you with this: Using dates, times and time spans in Calculations
However, regarding the fact that you can't get to the process attributes in the calculation, as the runtime values come from the process object that you are on (e.g. incident, request, etc) then calculation should also give you access to these same attributes as well. However we've just checked and it doesn't. I would suggest that you please raise this as a support case referencing this thread so that a new problem can be raised for this which will be sent to Development for review.
There is a possibility of a workaround by having a calculated attribute on the process object (e.g. incident, request, etc) and then a value type on your create end user action which would need to be set on a string attribute, then copied into a datetime attribute. A rather messy workaround in my view, so I would definitely encourage you to raise a support case please, even if you are able to find a workaround for the issue.
Thank you, Karen.
Already have a support call in
I did start working on something similar to your workaround, I'm being pushed to get this functionality up and running so am going have to try it that way and see how we go.
Hopefully the root issue can be fixed in future versions.
For anyone with similar issue, the workaround seems to work fine.
As this is over a year old how is the attention from development on this issue?
Any chance this gets fixed in a future version?