Primavera Unifier Configuration Package Adjustments
(Doc ID 2953094.1)
Last updated on JUNE 14, 2023
Applies to:Primavera Unifier Cloud Service - Version 23.1 to N/A [Release 23.1 to NA]
Information in this document applies to any platform.
The table below can be used by Unifier Administrators to make adjustments to the configuration included in the Unifier Essentials base configuration package. Depending on when your configuration package was imported and your subsequent updates to the configuration were made, you may want to consider applying these changes.
|Reason for Update
||Package Effective Date
|Project Status Business Process (BP), users are able to enter more than 100% Project Complete.||Add Validation that Project Complete must be between 0 and 100%.||12/2/2021||Unifier uDesigner|
|End Step forms were View Forms, which did not allow an update via REST.||Update workflow End Step form to an Action Form if BP will be updated via RESTful services.||12/21/2021||Unifier uDesigner, Integration|
|L1-L10 Financial Approvers may be the final approver on a BP record, which requires a new folder to be created so that the Custom Print can be saved to the Document Manager. Groups had inadequate Document permissions.||Ensure L1-L10 Fiancial Approvers have permission to create subfolders via Document Manager permissions.||1/6/2022||Unifier Administration|
|Owner Walk Through BP: "Title" was not a required field on the line item, causing auto-creation of the Punch List Item to fail if not populated.||Make the "Title" field required in the Detail Form of the Owner Walk Through BP.||1/11/2022||Unifier uDesigner|
|Submittal and RFI use restricted View Forms on terminal status records.||Update the end step forms to View forms for Submittal and RFI BPs.||1/25/2022||Unifier uDesigner|
|Payment Application field "B. Approved Change Orders" was auto-populated (from the Contract BP) on Payment Application creation and did not update if Change Orders BPs were approved while the Pay App was in flight.||The old data element was hidden and replaced with a Query Based Data Element that queries the Change Orders directly. The old data element was set to a formula equal to the new data element so existing records would not be impacted.||2/15/2022||Unifier uDesigner|
|Several data views were not including View-Only or On-Hold statused Project Shells.||Update the following data views, replacing "WHERE STATUS = 1" (Active status) with "WHERE STATUS != 0" (Not Inactive status): ue_cf_headers_all, ue_cost_sheet_org, ue_cost_sheet_pgm, ue_open_tasks_all, ue_pgm_summ, ue_proj_detail, ue_proj_phase_summ, ue_proj_summ, ue_task_analys, ue_user_group_mgmt||3/30/2022||Unifier Administration|
|Data Cube "Contingency Usage - Last 30 Days" was not supporting multi-currency.||Updage Budget Transfer line item field from "0 - Budget Transfer Line Item / Amount" to "0 - Budget Transfer Line Item / Amount in Base Currency"||3/30/2022||Unifier Administration|
|Document Approval BP: Unable to markup documents||Update Upper Form properties in uDesigner to allow modification of line items.||3/30/2022||Unifier uDesigner|
|Payment Application Custom Print Template formated the Cost Code as a number not a string, resulting in failure of CBS codes which includes letters to print.||Update the .rtf template for the Pay App BP (<?for-each:current-group()/uxuepya_lineitem[./INDENTLEVEL=1]?><?sort:ORDERID;'ascending';data-type='number'?>)||4/14/2022||Unifier Administration|
|Issue BP: User could select "Yes" to create a Change Request without entering a "Change Reason", which causes the auto-created Change Request BP to miss the required field.||Create a Dynamic Data Set to require the "Change Reason" field if user choosed to auto-create a Change Request BP.||4/29/2022||Unifier uDesigner|
|Payment Application BP: Possible to send record to next step for approval with negative balance to finish.||Moved Form Validation earlier in the workflow to avoid submitting Pay Apps with negative balance to finish. Validation was previously only on record final approval.||7/13/2022||Unifier uDesigner|
|Payment Application BP: Able to enter more than 100% Work Retainage % and Stored Material Retainage %.||Added Validation that Retainage % must be between 0 and 100%.||7/13/2022||Unifier uDesigner|
|Issue BP: User could select "Yes" for Cost and Schedule impacts without entering the impacts. This will create issues on auto-created Change Request records.||Add Dynamic Data Sets in uDesigner to forms where Cost and Schedule Impact fields are editable to require detail if "Yes" is selected.||8/9/2022||Unifier uDesigner|
|Two Data Views include a divisor equal to zero.||Update: ue_proj_summ (Project Summary text file) and ue_pgm_summ (Program Summary text file). See attached text files.||8/9/2022||Unifier Administration|
|Query Based Data Elements (QBDEs) using Amount in Project Currency.||Update QBDEs in BP Configuration to use Amount instead of Amount in Project Currency for the following BPs: Change Order, Change Request, Contract, Purchase Order, PO Amendment, and Invoice.||8/21/2022||Unifier Administration|
|The Financial Summary block on the Upper Form of some BPs displays incorrect results when records are creating in a currency that is not the Project Currency.||Remove the ability to create records in a non-Project Currency for the Budget Change, Forecast and Fund Appropriation BPs. Remove the Currency Block on the Upper Forms.||9/2/2022||Unifier uDesigner|
|Initial Budget BP may reset line item quantities to 1 when record is auto-created by an Estimate record.||Update Estimate BP setup for auto-creation of Intitial Budget to bypass the Initation Step during Auto Creation.||9/15/2022||Unifier Administration|
|Change Order BP was not allowing consolidation of line items from the Change Request.||Replace query conditions for the "Originating Change Request" BP data picker to match Project Number. This will only allow users to consolidate Change Request Line items from the same Project to the Change Order. Also, allow consolidation of previously consolidated line items when the Change Order status is "Canceled" or "Rejected." This allows previously consolidated Change Request line items to be selected on a second Change Order if the first Change Order is canceled or rejected.||10/27/2022||Unifier uDesigner|
|Data views ue_pgm_summ and ue_proj_summ will not run in DB Version 19c (Unifier 23.1). New DB is more restrictive.||Remove any duplicate alias from the data view. See attached Unifier 23.1 (Database v19) Unifier Essentials Data View Fix PDF.||1/18/2023||Unifier Administration|
|Budget Change Custom Print shows Current Budget as Initial Budget.||Replace the data element used for Initial Budget with the correct data element: "ue_gen_IBQBDE" on the Budget Change Custom Print .rtf Template.||3/20/2023||Unifier Administration|
|Data view "ue_news_feed" which provides data for Dashboards and Reports creates error: "sting concatenation is too long."||Update ue_news_feed Data View SQL. Replace row 324:
"REPLACE(nvl(OLDVALUE,''),'null','') || ' --> ' || REPLACE(nvl(NEWVALUE,''),'null','') as EVENTTEXT,"
with a Case statement:
CASE WHEN LENGTH(REPLACE(nvl(OLDVALUE,''),'null','')) > 50
THEN substr(REPLACE(nvl(OLDVALUE,''),'null',''),1,50) || '…'
CASE WHEN LENGTH(REPLACE(nvl(NEWVALUE,''),'null','')) > 50
THEN substr(REPLACE(nvl(NEWVALUE,''),'null',''),1,50) || '…'
END as EVENTTEXT,
|Special characters in Project Shell Number and Publish Path fields will cause Shell Creation and Document Publishing to fail.||Add Validation using Advanced Formulas to not allow special characters in Project Number, and Publish Path Fields on Project Request, Folder Template, Company Configuration, and Project Configuration BPs.||3/20/2023||Unifier uDesigner|
|RFB BP: The hidden Short Description field on the Bidder detail form prevents CSV upload of line items by Bidders.||Remove the Short Description field from the hidden block on the RFB Bidder Detail Form.||3/20/2023||Unifier uDesigner|
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