A BPA Process Enrichment script setting a custom Date/Time attribute's default value (using a plain JavaScript `Date` or its ISO string) fails, even though setting a text or user-identity default value in the same flow works fine.

All FAQ questions / Workflows and automation

Answer

The workflow engine only accepts a couple of specific DATETIME string formats, and neither a raw JavaScript Date object nor its default ISO-string output matches them — format the value explicitly (for example, using Java's SimpleDateFormat from a script task to produce a yyyy-MM-dd-HH.mm.ss-style string) before setting it as the execution variable feeding the custom attribute. See the workflow engine's directly-supported date/datetime formats.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Workflows and automation questions