SR-C84609 · Issue 424883
CustomFilter clipboard page now retained after section submit
Resolved in Pega Version 8.3
When a Report Definition was configured to display filters using a custom section, selecting the filter property value and submitting the section resulted in the CustomFilter clipboard page being deleted automatically. In order to prevent the clipboard page from being immediately cleaned up by the doUIAction activity, a step has been added to the pzCreateCustomFilterPage activity that will set the pyRetainPage property to "true".
SR-C86260 · Issue 424927
RecordsEditor Section- Parameters for HideDelete and HideAdd held on clipboard for use
Resolved in Pega Version 8.3
On initial load of a RecordsEditor section, the delete and add options were properly hidden from the user. After using any sort option on any column, the parameters were not persisted and the delete and add icons became visible. To resolve this, the implementation has been updated so that the pyHideDelete and pyHideAdd parameters will be read from myParamPage on the initial load and saved on a clipboard page for use.
SR-C83615 · Issue 424945
Support added for hiding unwanted category reports
Resolved in Pega Version 8.3
After upgrade, a customization used to hide unwanted out-of-the-box category reports was not working. This was due to the pyServiceLevelPerformance and pxSimulations category rules not being included as part of the pyOOTBVisibleInBrowser 'when' rule that is specified for Display in the report browser 'when' setting. These two category rules - pxSimulations and pyServiceLevelPerformance - have now been modified to reference the 'when' rule pyOOTBVisibleInBrowser so categories may be hidden as desired.
SR-C75536 · Issue 425013
Corrected agent scheduling issue for different server time zone
Resolved in Pega Version 8.3
When a server timezone and the agent schedule used different time zones, a server restart with cleared extract marker resulted in BIX agents no longer running automatically due to the next run showing as scheduled in the past. This was traced to the method used to compare start date time, and has been resolved.
SR-C84021 · Issue 425049
Lower major ruleset versions will not be considered during design time validation
Resolved in Pega Version 8.3
After circumstancing a rule by property and withdrawing the rule in higher version, the same rule was circumstanced by template. Later after major skimming, attempting to perform a save-as of the circumstanced template rule resulted in an error stating that the circumstanced property already existed. During design time, the system validated the rule with rules from all other ruleset versions. In this corner case where a property-based circumstanced rule was withdrawn and then skimming was performed, the error occurred because it was being saved in a different major ruleset instead of into the same major ruleset. In order to better handle this condition, the system will not consider rules from lower major versions during design time validation.
SR-C85752 · Issue 425072
New MaxFileSize extension point added for pyMaxFileSizeViolation
Resolved in Pega Version 8.3
A severe guardrail warning was raised when saving the activity pyMaxFileSizeViolation into a ruleset. This was traced to the CheckForWarnings Activity of Rule-Obj-Activity which checks if any activity referenced is an internal activity. Activity pyMaxFileSizeViolation was calling the internal pzGetCMMaxFileSize activity, and the warning appeared because the py activity was overridden in the application ruleset. To resolve this and add an extension point, pzGetCMMaxFileSize has been modified to a new data transform called pxGetCMMaxFileSize, which is called in pyMaxFileSizeViolation.
SR-C76412 · Issue 425188
Content type header removed from default inclusion in JWT token to support MS integration
Resolved in Pega Version 8.3
In order to integrate Pega with Office365 to use the Outlook API to Send and Get messages, an access token is required as a part of Authentication process. For obtaining an access token from the Azure directory, the process is to follow the OAuth 2.0 client credentials flow which requires the generation of a JSON Web Token (JWT) with the required Header, Payload and Signature. However, because Pega adds the tag "cty": "application/json" by default, using the out-of-the-box 'Token Profile' rule to generate the JWT and pass the same in a REST call to Microsoft was resulting in a error response indicating that there was an unsupported token header. This has been resolved by removing the content type header in the JWT token.
SR-C85853 · Issue 425287
Currency codes updated
Resolved in Pega Version 8.3
The list of Currency Codes has been updated with the latest ISO changes, including Venezuela and Sao Tome & Principe.
SR-C78006 · Issue 425510
Wait corrected for sub case after reopening
Resolved in Pega Version 8.3
A re-opened parent case was not waiting for the sub case when a sub case was reopened, but it did wait if there was no sub case on the reopened parent case. This has been resolved by enhancing the system to better handle the reopen of activator and dependent work objects by checking the reopen time: - pzGetAllStatusforDepClass activity: added step 2 to consider activator reopen time - pzGetMessageKeysForFlowDependencies list view: added criteria to filter on reopen time
SR-C81829 · Issue 425617
pxCoveredCountOpen value decrease corrected
Resolved in Pega Version 8.3
When a flow reached the resolved stage (Resolved-Withdrawn), pxCoveredCountOpen was reducing the count by 2 instead of 1, eventually causing the value to go negative and prevent any further work objects from being marked as Withdrawn. Investigation showed the "Update status" activity was being called twice due to the Temporary WorkPage used to delete assignments persisting and appearing as a duplicate pyWorkPage. This caused an issue when using findPage by pzInsKey. To correct this, the "pxDeleteAssignmentsForWork" activity for Step-15 has been modified to explicitly remove the temporary WorkPage after the assignment is deleted.