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.
SR-D18725 · Issue 488208
OrgUnit delete works as expected
Resolved in Pega Version 8.4
After creating two organization units such as Unit1 and Unit11 on the same level and mapping one operator to Unit11, attempting to delete Unit1 resulted in an error indicating the operator had to be deleted first even though unit1 had no operator associated with it. This was traced to Obj-List performing a 'like' check instead of exact match check for the deletion, and has been resolved by updating the ValidateDelete activity to do obj-browse instead of obj-list.
SR-D19999 · Issue 488268
Logic updated for displaying email attachments
Resolved in Pega Version 8.4
Once an Email had been sent with attachments, additional attachments could be added to the work object at a later time and would show up when the work object was opened as if they had been part of the original transmission of the message. This was traced to the logic not accounting for for the state of the data-corr-email object and showing all the work object attachments as sent as part of the email irrespective of when the attachment was added. To resolve this, the system has been updated to save all the attachment keys that are sent as part of the email on the data-corr-email instance and use that property while retrieving the list of attachments sent on the email. If the attachment is deleted, no hyperlink will be shown but instead a message on hover on the attachment memo will note that the attachment was deleted and not available for download.
SR-D22415 · Issue 493442
Enhancement added to expose BrowserAttachmentTypeTable
Resolved in Pega Version 8.4
By default, the inline view of PDF files appears with the thread name visible. An enhancement has been made to expose pzBrowserAttachmentTypeTable as a py rule: when the DT is overridden such that return is false for PDF, the inline view is not displayed but instead the PDF is downloaded when clicked.
SR-D23723 · Issue 503089
pxGenerateExcelFile updated for handling blank dates
Resolved in Pega Version 8.4
When using a custom template for exporting to Excel, blank DateTime property column values defaulted to the current date or to 1/1/1970. To resolve this, the pxGenerateExcelFile activity has been updated to ensure that an empty date will be exported as blank and that given dates will appear in the correct datetime format.
SR-D24470 · Issue 494628
Custom attachment category parameter passed to dropdown
Resolved in Pega Version 8.4
Attempting to use the out-of-the-box “Attachments control” which was configured at design time to use a custom category where both the custom category and the section class were in the same work class resulted in the attachment category dropdown defaulting to “File” instead of the custom category. Investigation showed that the custom attachment category name configured on the control was missing in one of the pre-processing activities sequence. To resolve this, the activity Work-.pzInitAttachContent and the initAttachmentPage activity have been updated to pass the custom attachment category parameter.