SR-B69406 · Issue 325269
GetLinkedSpecsForRule will preserve existing framework rule spec links
Resolved in Pega Version 7.3.1
When a framework layer rule was opened Specs were not listed, and checking out and checking in the rule caused the link to spec which was associated in the framework layer to also be deleted. This appeared as specifications created for the FW layer not being visible from the Rule form when the current access group pointed into the Implementation layer. It should be noted that the Framework layer specs cannot be linked with framework layer rules when doing development in the implementation layer - that is an expected behavior. Therefore the fix for this issue will just retain the existing rule specification links even for framework rules: On Report definition pzGetLinkedSpecsForRule context mode was changed to All Rules in Application and Frameworks except PegaRULES. PostCheckOut activity in following classes were updated to call PostCheckOut from Rule- Rule-HTML-Section Rule-HTML-Harness Rule-File-Stencil Rule-File-
SR-B77272 · Issue 326822
TransformerFactory security functions reverted
Resolved in Pega Version 7.3.1
Export to Excel was broken in the IBM environment. This was related to compatibility with security updates which were not consistently implemented by TransformerFactory installations. To resolve this condition, those security changes have been removed from the following functions: DCOdocumentToBytes DCOnodeToString DCOgetStringFromDocument
SR-B77713 · Issue 327047
Null check added to pxSystemFlow to handle post-upgrade assignment display
Resolved in Pega Version 7.3.1
After upgrade, assignments were not being displayed. This was due to pxSystemFlow being blank in earlier versions of Pega. In the Flows section the assignments are filtered based on false check, hence assignments were not seen. To prevent this issue, a null check has been added.
SR-B77745 · Issue 327019
pyCaseBreadCrumb control localized
Resolved in Pega Version 7.3.1
When viewing a case, the pyCaseBreadCrumb control was not localizing the value, instead always displaying the value of pyLabel. This has been corrected.
SR-B64309 · Issue 315889
PDN help properly reflects FlowAnalysis implementation in the Diagram tab
Resolved in Pega Version 7.3.1
The documentation has been updated in the PDN to reflect that the ruleform "Flow Analysis" option is no longer available. The references to this were mistakenly left visible due to a build issue and the help files have now been republished so they match the current implementation of the Flow Analysis option, which is available on the Diagram tab.
INC-167606 · Issue 665868
Updated ConfirmHarness handling for case type creation
Resolved in Pega Version 8.5.5
If a new case type was created with the initialization stage and there were no assignments in the case type, the /cases API did not return a NextPageID in response. This has been resolved by setting the pyConfirmHarness parameter before calling addworkobject.
INC-168368 · Issue 651080
Correct flow actions loaded in multi-thread portal refresh
Resolved in Pega Version 8.5.5
The member authentication screen was displaying an incorrect flow action on doing browser refresh after creating a new interaction. Refresh is a special case where the parameter retention is different across single-threaded & multi-threaded portals alongside the execution order of activities. In this case, this inconsistency occurred in a multi-threaded portal when newAssignPage had the information to load the proper assignment but the parameter indicated an old index. This has been resolved by adding 'when' conditions to to populate and pass the correct references and labels and to honor the Param.TaskIndex set and sent by UI activities so it's retained in case of multi-thread portals.
INC-169636 · Issue 649730
WorkObjects security update
Resolved in Pega Version 8.5.5
Cross-site scripting protections have been updated for WorkObjects.
INC-170514 · Issue 653761
Lock conflict resolved for AssignmentCheck
Resolved in Pega Version 8.5.5
The error "Unable to unlock this work object" sporadically appeared in both the runtime log and Pega RULES log when the robot was trying to create a case in Pega using an API call. Investigation showed that as the case was created, it was pulled by another robot (another requestor) which was using the GetAssignments API. This caused the perform assignment check to fail. To resolve this, a 'when' rule has been added to the performAssignmentCheck Activity.
INC-171842 · Issue 664385
Visible element populated for field value controls
Resolved in Pega Version 8.5.5
When implementing a section which had several labels with visible when conditions, this is not reflected in the DX API Get Assignment View. This has been resolved by adding a visible element.