SR-121758 · Issue 178251
Logic added to resolve conflicting Currency display values
Resolved in Pega Version 7.1.8
The read-only display format of the out-of-the-box Control 'Currency' was not working as expected due to a precedence conflict between the 'Property Qualifier' configured at the property level and the out-of-the-box 'Currency' control configured on the property in a section. For example, the Inquiry amount value in case details section under Overview tab was displayed as 100.00/$ when it should be displayed as 100.00/USD. To resolve this, logic has been added to check the ruleset qualifier settings.
SR-121758 · Issue 178990
Logic added to resolve conflicting Currency display values
Resolved in Pega Version 7.1.8
The read-only display format of the out-of-the-box Control 'Currency' was not working as expected due to a precedence conflict between the 'Property Qualifier' configured at the property level and the out-of-the-box 'Currency' control configured on the property in a section. For example, the Inquiry amount value in case details section under Overview tab was displayed as 100.00/$ when it should be displayed as 100.00/USD. To resolve this, logic has been added to check the ruleset qualifier settings.
SR-121758 · Issue 178251
Logic added to resolve conflicting Currency display values
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.8
The read-only display format of the Out-of-the-Box Control "Currency" was not working as expected due to a precedence conflict between the "Property Qualifier" configured at the property level and the Out-of-the-Box "Currency" control configured on the property in a section. For example, the Inquiry amount value in case details section under Overview tab was displayed as 100.00/$ when it should be displayed as 100.00/USD. To resolve this, logic has been added to check the ruleset qualifier settings.
SR-121768 · Issue 182217
Improved locking for check-out-enabled rulesets
Resolved in Pega Version 7.1.8
If a specification with an attachment is defined to a work flow in a check-out-enabled ruleset, then the generated specification and binary file rules were set to the checked-out state and could not be checked in. This was caused by the previous method for lock checking not consistently being applied in custom environments, and the locking has been changed to use an added condition on the InstanceLockedByRuleSet property.
SR-121768 · Issue 182807
Improved locking for check-out-enabled rulesets
Resolved in Pega Version 7.1.8
If a specification with an attachment is defined to a work flow in a check-out-enabled ruleset, then the generated specification and binary file rules were set to the checked-out state and could not be checked in. This was caused by the previous method for lock checking not consistently being applied in custom environments, and the locking has been changed to use an added condition on the InstanceLockedByRuleSet property.
SR-121820 · Issue 178865
Next button behavior in a modal dialog corrected
Resolved in Pega Version 7.1.8
A workflow issue was found with the 'Next' button on a last row of a repeating grid where clicking on the 'Previous' button would then improperly make available a previously grayed out 'Next' button. Similarly, clicking the 'Next' button on the next-to-last row fired the validation but then disabled the 'Next' button. This was traced to the "NextDisabled" parameter being set incorrectly in case of server side errors, and has been fixed.
SR-121820 · Issue 182933
Next button behavior in a modal dialog corrected
Resolved in Pega Version 7.1.8
A workflow issue was found with the 'Next' button on a last row of a repeating grid where clicking on the 'Previous' button would then improperly make available a previously grayed out 'Next' button. Similarly, clicking the 'Next' button on the next-to-last row fired the validation but then disabled the 'Next' button. This was traced to the "NextDisabled" parameter being set incorrectly in case of server side errors, and has been fixed.
SR-121825 · Issue 181670
Multiple annotations now allowed for swimlane objects
Resolved in Pega Version 7.1.8
When two annotations were used with swimlanes, the description in the annotation is unexpectedly changed or the annotation itself disappeared due to an ID conflict. There was a workaround of adding the shapes using the right click, but the annotation shape is now correctly added to the work flow using the proper unique ID.
SR-121828 · Issue 179859
Localization added for the "Loading" text of the busy indicator
Resolved in Pega Version 7.1.8
Previously, the 'alt' values of the "Loading" text for the pega_ui_busyIndicator (pxThrobber) were hard-coded to English. This has been changed to allow localization.
SR-121858 · Issue 183012
Added integration for Microsoft Azure Root Certificates
Resolved in Pega Version 7.1.8
Attempting to implement Single Sign On using MS AZURE AD was failing. This was due to the Microsoft Azure Root Certificates not being correctly configured/imported into the target Application Server. Microsoft Technical Support was engaged and recommended manually exporting the required certificate from Azure and importing into the target environment as a workaround, and this integration has now been addressed with updates to the XML Security ResourceBundle.