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.
INC-173944 · Issue 660180
Cancel button on embedded GridRow cancels single action
Resolved in Pega Version 8.7
When a modal Flow Action contained a Table with the Row operations configured as Master-detail and the Detail flow action was specified, if a validation error defined in a Validation rule (i.e. other than required field error) occurred while entering details for one of the rows and the Cancel button for that row was clicked, the entire action was cancelled and the modal window was closed without saving anything. This has been resolved by updating the system to prevent the modal closure if a row is added and then cancelled.
SR-125044 · Issue 187842
Ampersand(&) handled as text and not parameter for data transforms
Resolved in Pega Version 7.1.8
When passing a parameter to a data transform, if the parameter value contained an ampersand ('&') or certain other non alphanumeric characters, an error was generated (visible in tracer) and the task failed. This was a case where an '&' character was not not handled as literal text, causing the RunActionWrapper to explicitly parse it and create params out of it. There was a local-change solution to directly reference a property value containing the required text value instead of passing it in via a parameter, but the system has been updated to encode ampersand(&) in the file pzpega_ui_events.
SR-131430 · Issue 200005
Resolved error from empty repeating grid
Resolved in Pega Version 7.1.8
If a repeating grid is opened and no rows are added, the Microsoft Internet Explorer 8 browser was generating an error. When the grid is collapsed in the header its dimension parameters such as offsetHeight etc. are zero, so certain calculations in setHeadersWidth function in ui_grid js would fail and wrong dimension values would be assigned to the grid. Other browsers were failing silently in this situation, while Microsoft Internet Explorer 8 showed errors. To avoid any failure, a check has been added to the setHeadersWidth function in ui_grid js.
SR-123478 · Issue 186770
Defined order of execution for FinishAssignment and pyDeleteDocumentPg
Resolved in Pega Version 7.1.8
In an application in which a page-level message was to be output if a certain field was left blank, sometimes the page-level message did not display when the condition was met. This problem was due to the random order in which pyDeleteDocumentPg and FinishAssignment were issued by the Browser. Both are issued simultaneously to within the same 1000th of a second (according to Fiddler), but sometimes one is issued first, sometimes the other is issued first. Whether or not the function succeeded depended on whether or not pyDeleteDocumentPg was processed first by the server. In order to ensure the proper behavior, the submit and harnessOnBeforeUnload methods defined in pega.u.d object have been modified to send the finishAssignment request after processing the pzDeleteDocumentPg request.
SR-119297 · Issue 183495
Dynamic container enhanced for harness sections
Resolved in Pega Version 7.1.8
In some situations, tab visibility conditions were not functioning as expected. For example, in a portal with a harness that has 2 sections, the click of an enable/disable button in the top section was configured to refresh the bottom section as well as call an activity. The bottom section had a tab layout containing harness rules with conditions specified for the tab visibility based on the above "Enable/Disable" button. For the above features, the data model got created when the Dynamic Container was being rendered for the portal's harness, and the data model was updated with the dynamic tabs' meta data. However, the data model was not being created while rendering the harness, and the lower section did not confirm to expectations. To resolve this, the code has been updated to handle the section refresh which has a Dynamic Container.