Modified/Draft Data Is Not Populated to the Print Output
(Doc ID 2670981.1)
Last updated on MAY 22, 2020
Applies to:Primavera Unifier Cloud Service - Version 184.108.40.206 to 220.127.116.11 [Release 19.12]
Primavera Unifier - Version 18.104.22.168 to 22.214.171.124 [Release 19.12]
Information in this document applies to any platform.
On Unifier : Version 19.12.4
When creating a New Business Process (BP) record, the Custom Print does not render all of the data elements with the data from the BP record. However, after the document has been sent beyond the Creation step, then the Custom Print is generated as expected. This issue began after upgrade to 19.12.4. Before the upgrade the fields would be populated even on the create step. If you open existing BP record in the BP log, and use Custom Print, the fields are populated with expected data.
The expectation is that the Custom Print for the BP record will work as it did prior to the 19.12.4. upgrade, where using Custom Print on a BP record at Create step will populate all data.
The issue has the following business impact:
Due to this issue, users do not see expected fields populated on BP record at Create step when using Custom Print.
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