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-128960 · Issue 571360
Corrected approval step task message
Resolved in Pega Version 8.1.9
When a case progressed to the approval step, the task name did not properly appear as part of the "Please approve or reject this" message. In another scenario, a portal which supported locale switching was not translating "Please approve or reject this" when the locale was switched, but instead displayed the message in the original language. Investigation traced this to the pzInstructionsForApproval data transform storing the localized field value, causing it to persist inappropriately. This has been resolved.
INC-131151 · Issue 572832
Resolved empty body for Reject email
Resolved in Pega Version 8.1.9
When using the pzEmailActions Section in Correspondence for Approve/ Reject functionality via email, there was no reply body in the email for Reject Option. This was due to the flow action for the Reject email being different than that of the Approve email, and has been resolved.
INC-131385 · Issue 573454
Swagger APIs updated
Resolved in Pega Version 8.1.9
The Swagger File APIs have been updated to ensure swagger document files generated meet specifications for editor.swagger.io .
INC-134370 · Issue 577635
Expanded Grid locking updated
Resolved in Pega Version 8.1.9
When using pyDashboadMyWorkList to show the cases of an operator with Master Detail in Read Only mode, the system was acquiring a lock on the expanded work object. To resolve this, the following changes have been made: * In activity Assign-pyAcquireObject, If the parameter bRODetails is true, do not call acquireWorkObject and do obj-open-by-Handle to get assignment and work page in pyAcquireObject activity. * In activity acquireWorkObject, the parameter skipWorkLock has been removed as acquireWorkObject should always acquire the lock.
INC-134709 · Issue 579433
Updated endpoint Cross-site scripting protection
Resolved in Pega Version 8.1.9
Cross-site scripting security has been updated for Endpoints in Display activities.