SR-A2750 · Issue 211790
Made custom ruleset versions available when saving custom rule types
Resolved in Pega Version 7.2
When trying to save certain rules, users were getting a limited number of rulesets even though there were unlocked versions. Specifically, this issue occurred for custom rule types. The rulesets available were not the same as when non-custom rule types were utilized. This has been resolved by adding the class of custom rule type for required rulesets so that all required rulesets will appear in the dropdown.
SR-A10163 · Issue 221183
Fix added for accessing WO correspondence using Microsoft Internet Explorer11
Resolved in Pega Version 7.2
When using Microsoft Internet Explorer11, the error ?Error-Open Authoring control failed to load? was generated when attempting to access correspondence attached to a work object. This has been fixed.
INC-142223 · Issue 598647
Handling added for new case type using reuse case life cycle
Resolved in Pega Version 8.5.2
Creating a new Case Type in a branch ruleset using the 'Reuse case life cycle' option was not working, and the error "branch rulseset not a candidate" was generated. pxCreateCaseDataPages that are called as part of creating a case rely on Param.RuleSetName; generally this parameter is set in the param page when other assets are created. When Reuse case life cycle was selected, other assets were not created and param.RuleSetname was not set. This affected pxCreateCaseDataPages when branch parameter was provided. This was a missed use case, and has been resolved by setting param.RuleSetName from param.ruleset to fix the issue.
SR-A3895 · Issue 211401
Using page passed properly for replace current scenarios of Launch Harness
Resolved in Pega Version 7.2
The using page was not passed properly for replace current scenarios of Launch Harness. To correct this, the pzpega_ui_dynamiccontainer.js and pega_desktop_api.js have been updated to pass the correct page context for doUIAction request.
SR-A7951 · Issue 218577
Sort filtering updated for Repeat Grid using RD as source
Resolved in Pega Version 7.2
Using the Sort functionality as a filter was not working in a Repeat Grid where records were fetched using a Report Definition. This was due to the property passed to the RD function not being populated while generating unique values in the filters, and parameter values have now been added to the visible list if the column name is a function in pzGetGridColUniqueValues activity.
INC-148154 · Issue 602919
Hot Fix Manager updated to use installation order for schema import
Resolved in Pega Version 8.5.2
Schema changes were not being imported during the hot fix manager DL import process. Investigation showed this was due to hotfixes in the DL being iterated over from newest to oldest, causing older hotfixes to replace the value added to a map by the newer. To resolve this, the system has been updated to use hotfix install order, which considers selected and dependent hotfixes, rather than ordering newest to oldest. This ensures that newer table representations will override older rather than the other way around.
SR-A9136 · Issue 221836
Added loop avoidance when Service SOAP wizard encounters parent class with sub-pages
Resolved in Pega Version 7.2
The Service SOAP wizard was presenting properties as Input Parameters that appeared to have a repeating reference not actually present in the Data Class specified to process. The initial reported issue showed the wizard presenting Input Parameters such as "RequestPage1.RequestPage1.RequestPage1.RequestPage1.RequestPage1.RequestPage1.RequestPage1.RequestPage1...." increasing in length on each line. This was caused by a loop created while creating the service from the Service Wizard and specifying a class name which has siblings and a parent class containing pages of the child class. To avoid this, the system will break the loop if the parent contains the page property of the child class.
INC-151253 · Issue 607624
Hash comparisons adjusted for upgraded sites
Resolved in Pega Version 8.5.2
Existing Pega Diagnostic Cloud SSO URLs were not working after upgrade. This was traced to the previous tenant hash (or AG hash) having padding characters like ‘(’ which are no longer used in higher versions. This caused the tenant hash comparison during the SAML login flow to fail. To resolve this, the system will not compare an incoming tenant hash (in relay state) with a current platform tenant hash, but instead will rely on the “/!” pattern to identify the tenant hash in the relay state.
INC-130703 · Issue 597255
Operator provisioning on authentication service corrected
Resolved in Pega Version 8.5.2
When operator provisioning was triggered on user login via authentication service, the error "ModelOperatorName is not valid. Reason: declare page parameters not supported by PropertyReference" was generated. This was traced to optimization work that had been done on the expression evaluation for operator identification, and has been resolved by adding the required GRS Syntax support in the Operator Provisioning section in SAML and OIDC.
SR-A11400 · Issue 223194
Corrected JAWS reading hidden label
Resolved in Pega Version 7.2
When using accessibility mode, a label was read during screen navigation using the keyboard tab when the label was hidden on the screen display. To correct this, the ARIA label has been updated to consider whether or not aria-hidden="true".