A BPA Process Enrichment flow setting a value (like a Price Freeze flag) via Default timing on a customer order line works from a data standpoint, but then the page stops treating the record as genuinely new — for example, blocking entry of a part number.

All FAQ questions / Workflows and automation

Answer

Check whether the workflow's default-data response is including an ETag — Process Enrichment on Default timing normally shouldn't carry one, but if it ends up attached, the page starts treating what should be a brand-new, still-editable record as an existing one with concurrency control applied; explicitly clearing the ETag execution variable (setting it to null) in a script task before the response is returned removes this side effect and restores normal new-record behavior on the page.

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