SR-B50202 · Issue 308172
Pre- and Post-processing modified to support customized circumstanced FA
Resolved in Pega Version 7.3.1
A customized out-of-the-box Flow Action called "CheckIn" was created by modifying a circumstanced version with property .pxObjClass = Rule-Admin-Product. For any Product rule, attempting checkin called this customized Flow Action as expected. However, the pre-processing activity and post-processing activity added in the circumstanced Flow Action "CheckIn" were not invoked at all; instead, the pre-processing activity and post-processing activity in the base Flow Action "CheckIn" were triggered. This was due to circumstancing not working when used with the doAction() method because it does not reset the primary page when it invokes a rule. It passes a step page for use by the rule. In order to support this customization, the function will call to tools.doActivity() with the same arguments instead of doAction(), which will force the engine to push myWorkPage as the new primary page for the duration of the call (and then pop it after the call completes). This should provide the correct context for the circumstancing to call the circumstanced purpose code.
SR-B63171 · Issue 315061
Pre- and Post-processing modified to support customized circumstanced FA
Resolved in Pega Version 7.3.1
A customized out-of-the-box Flow Action called "CheckIn" was created by modifying a circumstanced version with property .pxObjClass = Rule-Admin-Product. For any Product rule, attempting checkin called this customized Flow Action as expected. However, the pre-processing activity and post-processing activity added in the circumstanced Flow Action "CheckIn" were not invoked at all; instead, the pre-processing activity and post-processing activity in the base Flow Action "CheckIn" were triggered. This was due to circumstancing not working when used with the doAction() method because it does not reset the primary page when it invokes a rule. It passes a step page for use by the rule. In order to support this customization, the function will call to tools.doActivity() with the same arguments instead of doAction(), which will force the engine to push myWorkPage as the new primary page for the duration of the call (and then pop it after the call completes). This should provide the correct context for the circumstancing to call the circumstanced purpose code.
SR-B65755 · Issue 314416
Broken-Process SLA update API changed
Resolved in Pega Version 7.3.1
When an SLA update on a work object occurred and the current SLA was in Broken-Process Status, the action failed with the error "The Flow Action post-processing activity ActionChangeAssignmentSLAProps failed: Instance of class Queue not found". This was an issue where dequeuing the SLA entry item to update it with new time caused a status conflict with the blob. To avoid this, the activity ActionChangeAssignmentSLAProps has been updated to use the API updateDeferred(page,repairBroken) which accepts a Boolean if it has to repair a broken item. Setting the repairBroken flag to 'true' will bypass the call to dequeue.
SR-B47122 · Issue 308714
Fixed null-pointer exception for adding file to social media
Resolved in Pega Version 7.3.1
An null-pointer exception caused failure when adding a file to social media. This was traced to a missing null check in the function isRegisteredOnBeforeSubmit in the pzpega_social.js file, and has bene fixed.
SR-B53145 · Issue 317256
Back button on Survey screen works with validation
Resolved in Pega Version 7.3.1
If a Survey screen that validates a question failed that validation, the proper error was generated when the criteria did not match. However, clicking the 'Back' button on the screen caused the validation message to disappear while remaining on the current screen and not returning to the previous screen. This was due to a faulty IF condition in the setValue in SurveyAccessMethodBodyQuestion function, and has been fixed.
SR-B55628 · Issue 315581
New check added for stale clipboard data in StarDependencies
Resolved in Pega Version 7.3.1
When both pyWorkCover and pyTopCaseWork were on the clipboard, the pzStartDependencies function renamed the pyWorkCover to pyTopCaseWork and again back to pyWorkCover after calling pzStartSubCases. However, pyWorkCover had stale data due to this renaming when multiple resolve activity calls happened, leading to pxcoveredcountopen to not decrease when a child case was auto resolved. This stale data occurred due to a known issue with the milliseconds of date time property being rounded when stored in the database column of an SQL server. The resolution is to provide a new overloaded method of OpenIfStale with parameters to skip the deferred list and maintain locking strategy; this will be used in the out-of-the-box Resolve activity instead of Obj-Browse to see if the page is stale.
SR-B56088 · Issue 317045
Revised BuildQuestionPageStream to ensure proper doAction firing
Resolved in Pega Version 7.3.1
Validation was firing before reaching the question page in BuildQuestionPageStream section. This was due to the doAction being called without any check despite a conditional getstream configuration. To fix this, the BuildQuestionPageStream code has been revised to ensure doAction will not be called if the questiongroup is not the current questiongroup.
SR-B56142 · Issue 315911
Decoding support added for localized pyMessageKey
Resolved in Pega Version 7.3.1
When using FormattedText control, pyMessageKey was displaying encoded special characters in some scenarios. This was due to the InstructionsLookup control being used to show the localized value but the Pega lookup tag did not have a mode set to allow decoding. This has been resolved by adding logic to decode received localized text.
SR-B57171 · Issue 317890
pxSystemFlow populated after migration
Resolved in Pega Version 7.3.1
After a major upgrade, old cases did not have the pxSystemFlow property populated. This was due to a missing null check for the migration and has been fixed.
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.