SR-B159 · Issue 272693
Wizard will halt if rules to be deleted are in locked rulesets
Resolved in Pega Version 7.3
After running the Connector and Metadata wizard using a WSDL metadata file and then locking the current ruleset version, running the same wizard again using the same WSDL file and selecting OverWrite in the OtherConflicts step caused the rules in the locked first ruleset to also be overwritten. To prevent this, the CompleteRuleGeneration activity will cause the wizard to halt if it encounters rules that would be deleted that are in locked rulesets. When the ruleset(s) are unlocked, the wizard will continue.
SR-B16230 · Issue 287871
Dollar sign character will be escaped if present in data page value
Resolved in Pega Version 7.3
If a section was configured to show the data with a data page as source, using the dollar sign in the value caused the amount to not be displayed correctly in the grid. This has been corrected by adding code to escape the $ character when it's present in the data.
SR-B16328 · Issue 286668
BLOB data save performance improved
Resolved in Pega Version 7.3
In an installation with many large work objects, performance issues were seen when saving a BLOB. This was due to the BLOB still saving data for properties that had been removed, and has been resolved through better tracking of orphan entries of list type properties like string list and java object list.
SR-B16331 · Issue 303039
Check added to WorkUnlock to ensure cover page exists
Resolved in Pega Version 7.3
An intermittent error was logged related to workunlock. This was caused by Work-.Close calling workUnlock from the param.coverPage without performing a check first to ensure that the coverPage exists and has a class. To fix this, the WorkUnlock activity has been modified to verify that the coverPage has a class before unlocking the cover object.
SR-B16331 · Issue 294717
Cover page check added to Work-Close
Resolved in Pega Version 7.3
An intermittent stack trace was being generated in Work-Close; this has been resolved by adding a check to ensure that the coverPage exists and has a class.
SR-B16337 · Issue 287224
BIX TotalInserts and TotalInstance counts made consistent for nested pages
Resolved in Pega Version 7.3
The pxTotalInsertsCount and pxTotalInstanceCount values were being calculated incorrectly when using PageLists and a Page under those PageLists. This was a missed case, and the system has been updated to address it.
SR-B16337 · Issue 288963
BIX TotalInserts and TotalInstance counts made consistent for nested pages
Resolved in Pega Version 7.3
The pxTotalInsertsCount and pxTotalInstanceCount values were being calculated incorrectly when using PageLists and a Page under those PageLists. This was a missed case, and the system has been updated to address it.
SR-B16784 · Issue 287160
Attachments removed when work object withdrawn
Resolved in Pega Version 7.3
After adding an attachment and then withdrawing the case, the unneeded attachments were still being stored in the attachments section until a refresh was performed. This was traced to code in the UpdateAndDeleteAssignments activity that appended the target page rather than replacing. This has been modified to ensure attachments are eliminated when the status of a work object is moved to 'Withdraw'.
SR-B16825 · Issue 292599
WordMacroManagerDot updated for 64-bit compatibility
Resolved in Pega Version 7.3
The WordMacroManagerDot macro has been updated for Word-64-Bit environment compatibility.
SR-B16921 · Issue 287323
BIX documentation for Obj-Save help updated
Resolved in Pega Version 7.3
The BIX Extracts help file has been updated to clarify which properties are or are not updated when using Obj-save, explicitly noting that pxUpdateDateTime is not updated in the database when the Obj-save method is invoked and that a data transform should be applied to cause an update. Obj-save does update pxCommitDateTime.