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-138348 · Issue 599772
Added parameter skipPropertyEvaluation to handle CSS in email HTML
Resolved in Pega Version 8.4.4
While sending an email with custom HTML appended to the email body, a "+" sign in the body was causing the correspondence generation to fail. Investigation showed that if there were CSS classes with braces in the message body, the braces were being removed and replaced via "+" symbol in step 21 of CorrCreate activity. To resolve this, a new Boolean parameter skipPropertyEvaluation has been added in the CorrCreate activity to handle the decision to either evaluate the logic or not, and the pre-requisite will be to resolve all the property references before calling this activity so custom CSS braces { } will be honored when the message body is sent.
INC-140266 · Issue 602076
Search made consistent across environments
Resolved in Pega Version 8.4.4
Search was behaving differently based on whether the user was launching the search by clicking the search icon or hitting enter directly. The search icon passed the classes list and fetched cases based on that, whereas hitting enter performed the search without the classes list unless it was a multi-tenant environment. This has been resolved by updating the pyWorkIDSearch activity to pass application classes list in any environment.
INC-143025 · Issue 600611
API performance improvements
Resolved in Pega Version 8.4.4
Performance improvements have been made for running the get assignment action details API.
INC-144265 · Issue 609287
Updated timestamp handling for duplicate key issue with PyCompleteAutomation
Resolved in Pega Version 8.4.4
Occasionally a robot failed to complete a case due to a duplicate key exception. This was an issue with the History record creation due to duplicate key erlated to the timestamp, and has been resolved by updating the timestamp handling so that the REST API will use 'getCurrentTimeStampUnique' and for other cases 'pxGetCurrentTimeStampThreadUnique' will be used.
INC-144358 · Issue 601014
Localization added for "Automatically" and "Manually" field values
Resolved in Pega Version 8.4.4
The Dutch translation of "Child case [Case_type] [Case_id] has been [Instantiation_mode] instantiated" used the hard-coded English expression "manually". This has been resolved by adding the "Automatically" and "Manually" field values to localization.