Auto-Population From a Constant Value Configured on Any Other Form Being Used in the Workflow Other Than the Creation Step Fails
(Doc ID 2563838.1)
Last updated on OCTOBER 17, 2019
Applies to:
Primavera Unifier Cloud Service - Version N/A and laterPrimavera Unifier - Version 9.7 and later
Information in this document applies to any platform.
Symptoms
On Unifier : Any Version
When Auto-Population from a Constant Value is defined on any form being used in the workflow, other than the one defined for the Creation step, the value fails to be populated at run-time.
Example: On a four step workflow, Action Form 1 is defined for the Creation step and it does not have the auto-population defined, Action Form 2 is being used for the other steps in the workflow and it does have the auto-population defined.
The expectation is that when the user accepts the task at the second step the values should be auto-populated with the constant value.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |