SR-122409 · Issue 182081
Refresh when active' tabs no longer affecting other tabs
Resolved in Pega Version 7.1.8
A tab using the 'Refresh when active' setting, could cause the content of other non auto refreshing tabs to re-execute. E.g. Report Definitions that are sourcing repeat grids in other tabs. This occurred when using the 'Refresh when active' setting on a tab whose content is a Dynamic Layout (the out-of-the-box default when adding a tab) with an embedded section. There was a local workaround of updating tabs to use the required section as the top level content rather than using a dynamic layout with an embedded section, and this has now been incorporated into the software. The refresh when active setting is still available in this configuration.
SR-122413 · Issue 182457
Corrected button disable failure for values starting with '0'
Resolved in Pega Version 7.1.8
The button disable condition was failing for string values proceeded with zeros. To resolve this, the evaluate function of pega_ui_doc now has a check to not execute the parsefloat in cases of string and zero values.
SR-122440 · Issue 183753
Corrected text wrap for cases
Resolved in Pega Version 7.1.8
Text wrapping was not happening automatically in long history descriptions in a case. This was due to a missing function and has been corrected.
SR-122451 · Issue 184656
Smoothed multi-access group switching
Resolved in Pega Version 7.1.8
In the user portal, there is an option to change the access group to switch between the applications. There was no problem changing the access group the first time, but after creating a work object it was not possible to change the access group again. This was caused by the NavigationHeading - Changes table-layout CSS property value being set to "auto" , and the handleWidgets method has been changed to use the getAttribute method instead.
SR-122481 · Issue 189776
Issue with layout visibility condition expression formatting corrected
Resolved in Pega Version 7.1.8
After migration, the layout visibility condition expression was not working when given a value starting with zero in quotes (e.g. .tansactionstatuscd=='014'), although removing the single quotes or the zero caused the rule to evaluate to true. Previously, expressions were evaluated on the server side only but recent architecture changes moved this to the client side where such expressions were not supported. In order to ensure correct behavior, single quotes will be removed rom the given visible 'when' condition so the evaluation returns the expected result.
SR-122481 · Issue 186751
Issue with layout visibility condition expression formatting corrected
Resolved in Pega Version 7.1.8
After migration, the layout visibility condition expression was not working when given a value starting with zero in quotes (e.g. .tansactionstatuscd=='014'), although removing the single quotes or the zero caused the rule to evaluate to true. Previously, expressions were evaluated on the server side only but recent architecture changes moved this to the client side where such expressions were not supported. In order to ensure correct behavior, single quotes will be removed rom the given visible 'when' condition so the evaluation returns the expected result.
SR-122493 · Issue 190767
Support added for conditional page list properties
Resolved in Pega Version 7.1.8
After upgrading, validate rules on aggregate properties had unexpected behaviors. This rule formation was inadvertently allowed in some earlier versions despite guardrails, so support for these conditional page list properties has been added in order to enhance backwards compatibility.
SR-122500 · Issue 183869
Smoothed use of Row Repeat with a Repeating Grid that shares references
Resolved in Pega Version 7.1.8
Issues were found with the display of Row Repeat. It was not displayed when a section contained a repeating grid and row repeat layout that had the same pagegroup property reference, and in other cases was displayed improperly after taking the wrong class for a 'when' condition. The failure to display was due to the active page being the last page of the page group as set by Repeat Grid. The RepeatGrid layout generation was changed beginning in v6.3 onwards, and now uses a method-based engine. However, the RowRepeat layout has been deprecated and therefore still uses the previous generation method. This difference creates a conflict when the RowRepeat kicks off in the same stream generation. Furthermore, this issue arises only when the two layouts bound to same PageGroup property source, and not with a Pagelist property. To resolve this, the system now resets the activePage to that of the primary page in case of page group data source in the Repeat Grid generation so that the Row Repeat gets the proper active page for its generation. The issue with displaying when it should not has been resolved by retaining the existing business logic wherever the section rule with body visible when condition is used in a repeating layout.
SR-122504 · Issue 189293
Made operator identification consistent across flows
Resolved in Pega Version 7.1.8
A naming difference was seen in work flows depending on whether Visio or modular functions were used: Visio picks the "Task_Assignment2" function to generate java for assignment, giving the operator ID, but modular flows use "Task_Assignment" and show the operator name. In order to show consistent behavior, the code has been modified such that it first gets the operator name from the assign page if it exists, and it does not exist it will fall back to sending the operator ID as parameter.
SR-122513 · Issue 184655
Resolved missing alert for dirty Dynamic Select pages
Resolved in Pega Version 7.1.8
At runtime when the user selects some value in first dynamic\c select and tries to close the work object by clicking on the red cross mark(X), the expected dirty form alert message was not appearing. The system should set SectionReloaded to true to trigger an alert in this circumstance, but in this was not happening for this case and has been corrected.