SR-B57192 · Issue 315081
Performance enhancement added to optimize evaluation of 'when' calls in GetFlowData
Resolved in Pega Version 7.3.1
A lot of when conditions triggered as part of GetFlowData out-of-the-box activity were causing slowness when the Java Step (4) did its evaluation. Current screen flow navigation would evaluate all the when rules till the end of the flow to determine the flow navigation. To improve performance, an enhancement has been added to the GetFlowData activity to prepare pyFlowData page from the pyWorkPage. This will build the pyFlowData up to the current step and ignore the future steps. It will be necessary to override the PerformDefaults to pass the new parameter loadNavigationPathForBreadCrumbOnly to GetFlowData to call this new functionality.
SR-B64253 · Issue 321102
pyUsage field cleared in bulk process transfer
Resolved in Pega Version 7.3.1
In Bulk Process, auto-fill of audit notes is based on the pyUsage field on the NewAssignPage. Depending on the trigger method, the property pzBulkProcessItem of either the Work class or Assign class is called. In one of the classes, there is logic to explicitly clear or not copy the pyUsage Field. However, one of them had the value persist despite this, and the behavior differed depending on whether the activity called was Assign- pzBulkProcessItem or Work- pzBulkProcessItem. This was traced to the pyUsage property not getting cleared when "Transfer" was used while processing. In order to create consistent behavior, Work-.pzBulkProcessItem has been modified to not set the value to the clipboard when pyUsage is the property name.
SR-B64439 · Issue 315381
Replaced missing Survey category field on landing page
Resolved in Pega Version 7.3.1
The Survey category field was missing on the Survey landing page even though it existed on the Survey rule form. This field was mistakenly removed from the frequently used configuration options shown on the new landing page, and has been replaced.
SR-B66551 · Issue 317443
Fixed downstream question flow when upstream answer changed
Resolved in Pega Version 7.3.1
Downstream question responses were not getting reset on the form when a complex question (upstream question) response was changed. To fix this and to keep the behavior consistent, the property will be removed from both the survey embedded structure and the property mapping. BuildQuestionStream has been modified to clear the embedded answer value if the display when evaluates to false.
SR-B67238 · Issue 317283
UI Rendering API parameter updated
Resolved in Pega Version 7.3.1
The UI API's parameter resetTemplatingUIStatus setting of 'A' in On section - BuildQuestionStream has been deprecated. In some installations this caused localization to fail. To fix this, the resetTemplatingUIStatus setting has been modified from 'A' to 'Y'.
SR-B67327 · Issue 317826
pxUrgencyWorkStageSLA properly resets when no SLA on next stage
Resolved in Pega Version 7.3.1
pxUrgencyWorkStageSLA was not being reset when the next stage did not have an SLA. This has been resolved.
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.