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.
SR-121969 · Issue 184370
Deleted attachments flow error fixed
Resolved in Pega Version 7.1.8
If an attachment was added and submitted and then deleted from the attachment tab, the application then generated an error. This was caused by the system passing an invalid FromFrame after closing the modal dialog, and the code has been updated to use the originalFromFrame value when launching the flow.
SR-121980 · Issue 181118
Microsoft Internet Explorer 11 support added for auto-complete with multiple line properties in Report Definition
Resolved in Pega Version 7.1.8
If a property in a column of ReportDefinition that contains a carriage return (in order to input and display the value on two lines in the results) was then used as a source to Autocomplete control, then autocomplete control was not displaying the results. This was caused by a broken display with the Microsoft Internet Explorer 11 browser in compatibility mode, and code has been added to escape the new line character before converting the string to a JSON object so it will display as expected.
SR-121993 · Issue 181639
Fixed handling issues with substitutions enabled Parse XML rules
Resolved in Pega Version 7.1.8
Parse XML rules generated from an XML schema (xsd) saved in draft and "Not available" were generating Java errors when attempting to check out the rules and make them available. This happened when there were substitution elements and an embedded reference to the same element, and was caused by improper handling of the substitution helper method. This has been corrected.