SR-125990 · Issue 189549
Fixed row expansion issue in repeat grid
Resolved in Pega Version 7.1.8
When a modal dialog was being launched from a button in a repeat grid that was configured with expand pane and had the option checked for "Expand Multiple Rows", clicking on the Next/Previous button caused the second row of the the repeat grid to be expanded by default. This was a nested grid issue, and has been fixed by clearing string parameters.
SR-126011 · Issue 195418
RUF 'hasMessages' working with Declarative Pages
Resolved in Pega Version 7.1.8
Attempting to execute a Declarative Page with the RUF 'hasMessages' as a precondition caused a NPE. The error was caused by a null page call, and has been corrected by adding a null check for pageVarName and adding a find page call.
SR-126011 · Issue 195591
RUF 'hasMessages' working with Declarative Pages
Resolved in Pega Version 7.1.8
Attempting to execute a Declarative Page with the RUF 'hasMessages' as a precondition caused a NPE. The error was caused by a null page call, and has been corrected by adding a null check for pageVarName and adding a find page call.
SR-126031 · Issue 188833
Escape added to allow double quotes in UI read-only expressions
Resolved in Pega Version 7.1.8
In the Read only expression under the presentation tab of the properties panel for a section, including an expression which contained double quotes blocked the UI from being rendered. Upon analysis it was found that the characters were not properly escaped, and this has been fixed.
SR-126044 · Issue 189648
Rule resolution class search corrected for performFlowACallback function
Resolved in Pega Version 7.1.8
When performing an operation on a grid and then switching to local action, the thread name was being appended as undefined. This was caused by the rules search running on @baseclass instead of the framework class. A null check has been added to the performFlowACallback function to correct this.
SR-126051 · Issue 188520
External assignment goal execution corrected
Resolved in Pega Version 7.1.8
When an external assignment was created and correspondence generated to provide the external link, using Goal Execution to send a follow up was not working as expected after migration. Previously, the .CorrHandle property was stored and retrieved from the pxflow pages with a reference to the main flow which contained the External Assignment, and the "ExternalGoal" activity used the CorrHandle property to retrieve the correspondence and send a follow up. This was no longer working as the .CorrHandle property was relocated under a different page (VerifySendCorr). CorrUpdate has been modified to handle the flowname properly.
SR-126075 · Issue 192229
Added error handling for nested Tree Grid submit function
Resolved in Pega Version 7.1.8
When using a nested tree grid with a modal dialog that had a section Errors(section) from @baseclass, clicking the "save" button in the popup hid the files shown in the expanding area. This has been fixed by explicitly clearing the "partialTrigger" parameter set by the parent grid for the function SubmitModalFlowAction if there are errors in interest page.
SR-126082 · Issue 190051
Accessibility enhanced for navigating repeating grid search results
Resolved in Pega Version 7.1.8
An accessibility enhancement has been added to enable full keyboard navigation through the search results of a repeating grid in read-only mode. Double-clicking on a search result item opens the item in review mode in a separate tab, and the same functionality has been added which will open the tab by pressing the enter key on the item.
SR-126092 · Issue 189635
Enhanced logging for SQL exceptions with BIX
Resolved in Pega Version 7.1.8
In order to enhance diagnostics while using BIX, logging has been added to print the stack trace for an SQL Exception while fetching the last updatedatetime.
SR-126110 · Issue 189593
Adjusted custom header SOAP handling
Resolved in Pega Version 7.1.8
When a Soap connector request has custom headers, the values of the headers were blank; the tags were getting populated but with blank values in-between. This as an issue with the configuration under Rule-Connect-SOAP for the recent enhancement AddCustomHeadersToSoapEnvelope, and has been corrected.