SR-B6704 · Issue 289314
Auto-populate updated for better page copy references
Resolved in Pega Version 7.3
After upgrade, an error was generated at a page-remove step on the Group information screen while running the quoting process. This happened in cases where a copy was made of a page containing an auto populate property and the data page referred by the AP had Common Parent references, and was traced to the parent page of the reference property having been removed from the common parent page. To resolve this, the auto-populate function has been updated to better maintain references in copies.
SR-B6770 · Issue 280879
Cleanup improved for embedded page properties
Resolved in Pega Version 7.3
pyPreviousValues was retaining embedded page properties that were no longer used in pyWorkPage, causing the field level auditing to fire and write to the audit history every time the work object was updated. This has been resolved by changing the function rule pzAddHistoryMemoForScalar to remove an embedded page property in pyPreviousValues when the property is removed from pyWorkPage.
SR-B6904 · Issue 278482
Ensure CallVirusCheck is called only after populating data in UploadedFilePage
Resolved in Pega Version 7.3
Pega 7 provides the out-of-the-box extension activity Data-WorkAttach-File.CallVirusCheck which is intended to be customized with virus checking functionality to check the content of uploaded files. However, placing the activity too early in the customized process meant the check would not be correctly performed. To correct this, CallVirusCheck and the subsequent Property-Set-Messages steps have been moved to the end of the @baseclass.pzFileUploadGadget activity to ensure the existing java step populates file information on the UploadedFilePage and makes it available for the CallVirusCheck activity.
SR-B6971 · Issue 285310
Error propagation corrected for RDB-Save with RunInParallel
Resolved in Pega Version 7.3
If several Connect SQLs were called via the RDB-Save activity method with RunInParallel selected, failure of one of the Connect SQLs was not being caught and no errors were captured. This was traced to a situation where an exception thrown at the childcase with this combination of settings was propagated to the parent, and has been corrected by adding a Data-Admin-System-Setting "isPropagateExceptionFromChildToParent" defined in "Pega-RULES" ruleset, which has a default value of "true" only for RDB-Save method (not for all RDB-methods).
SR-B6971 · Issue 279537
Error propagation corrected for RDB-Save with RunInParallel
Resolved in Pega Version 7.3
If several Connect SQLs were called via the RDB-Save activity method with RunInParallel selected, failure of one of the Connect SQLs was not being caught and no errors were captured. This was traced to a situation where an exception thrown at the childcase with this combination of settings was propagated to the parent, and has been corrected by adding a Data-Admin-System-Setting "isPropagateExceptionFromChildToParent" defined in "Pega-RULES" ruleset, which has a default value of "true" only for RDB-Save method (not for all RDB-methods).
SR-B6980 · Issue 278169
fixed naming in multiple extracts run from the command line
Resolved in Pega Version 7.3
When running multiple comma separated extracts at a time using command lineoption -i, all of the rules in the manifest file contained the value of the last extract name only. This was a missed use case, and ExtractImpl has been modified to correct it.
SR-B7225 · Issue 277783
BIX documentation updated for Extract Rules
Resolved in Pega Version 7.3
The documentation outlining best practices for using BIX has been updated to reflect that when extractions are being run asynchronously there must be enough threads for each of the concurrently running extractions. The section "Running an Extract rule using a Pega 7 Platform agent" has been updated to read: "Number of concurrent extracts scheduled has to be limited based on the prconfig "agent/threadpoolsize." Set the prconfig setting agent/threadpoolsize to the max number of concurrent extractions you will be executing. The default value for this setting is 5 and the maximum value is 10.
SR-B7355 · Issue 277915
Actions visible in Perform harness for cases without active assignments
Resolved in Pega Version 7.3
When a stage configured with SLA did not have any active assignments, local actions could be launched from the Review harness but were not visible in the Perform harness. This was caused by the handling for cases without active assignments: virtual assignments are used to process the stage/case wide local actions, but the name of the virtual assignment page was not set and therefore not available later to fetch the local/flow actions. To resolve this, the assignment page name will be checked and set if it is empty.
SR-B7620 · Issue 289885
PopulateCaseContents activity updated
Resolved in Pega Version 7.3
The PopulateCaseContents activity has been updated to better handle missing or empty properties to ensure the flow name and RefObjectClass values are populated properly.
SR-B7620 · Issue 290018
PopulateCaseContents activity updated
Resolved in Pega Version 7.3
The PopulateCaseContents activity has been updated to better handle missing or empty properties to ensure the flow name and RefObjectClass values are populated properly.