Using SET FIELD VALUE action, ${out:dateTimeField} uses system timezone rather than user's

Question

Using SET FIELD VALUE action, ${out:dateTimeField} uses system timezone rather than user's

Closed this issue 8 years ago · 1 comments

We have a SET FIELD VALUE action in our document's custom logic that sets a General field to ${out:dateTimeField} (dateTimeField is specified as a DateTime field that includes the timezone output specification), the timezone value stored in the general field is the timezone of the deployment, not of the logged in user who's actions triggered the SET FIELD VALUE action.

Answer 1 · 2016-07-07T22:39:12.000Z

Fixed so the date-time uses the user's timezone (when the party is a logged in user) for the action. If no such TZ can be found, then it uses the deployment's default TZ.