SR-118735 · Issue 175180
Addressed ruleset integrations problems using Google Chrome
Resolved in Pega Version 7.1.8
When using Google Chrome and running the Integration > Tools > Rule-From-File wizard, the ruleset version was not displayed and it was not possible to proceed past the screen that requires values for rule name, ruleset, ruleset version and class name. This was due to there not being an input field for RuleSet Version, and the validation of that step in the wizard fails. This issue occurred due to Google Chrome not supporting the use of document.all in the HTML code, leading to an undefined value for the JavaScript. This has been resolved by changes to the HTML to make it browser code independent.
SR-118827 · Issue 179258
Work object reloading added to SFA portals
Resolved in Pega Version 7.1.8
When a work object in an SFA default portal (such as SFA SalesManager and SFAAdministrator) was opened by multiple users, modifications made by one were not seen by the other unless the other completely logged out and back in again. This was a function of the way the work object was opened and held in a thread, and has been modified with an API to reload the work object each time it is opened so that any saved changes are immediately available.
SR-119090 · Issue 179954
Progressive Paging Header Alignment Issue corrected
Resolved in Pega Version 7.1.8
On page load, the column headers for repeat grid with expand details did not align with the data when using Progressive Pagination. The root cause of this problem was with the design of Repeat Grids with 'Pagination' and Expand Details involved: the headers for Repeat Grid were created as separate table which failed to synchronize size with the table containing the data. To resolve this, changes were made in the GenerateGridHTML Function.
SR-119090 · Issue 175018
Progressive Paging Header Alignment Issue corrected
Resolved in Pega Version 7.1.8
On page load, the column headers for repeat grid with expand details did not align with the data when using Progressive Pagination. The root cause of this problem was with the design of Repeat Grids with 'Pagination' and Expand Details involved: the headers for Repeat Grid were created as separate table which failed to synchronize size with the table containing the data. To resolve this, changes were made in the GenerateGridHTML Function.
SR-119103 · Issue 178373
Missing hyphen auto-added to base class by import wizard
Resolved in Pega Version 7.1.8
When running the Connector & Metadata wizard to import the XSD file, entering the base class name without a dash created classes and properties all concatenated with the class name. However entering a dash at the end of the base class name created properties separated with the dash from the class names. This was an error in the wizard - it is no longer mandatory to end the abstract class with a dash, and the code has been updated to correctly append the hyphen at the end of baseclass if one doesn't exist.
SR-119214 · Issue 175331
Stream XML generation and runtime handling enhanced for optional nodes in schema
Resolved in Pega Version 7.1.8
When a stream rule was executed using connect-SOAP and blank data was passed from the UI, a tag corresponding to the XML element marked as optional was being generated. This resulted in those optional properties being unexpectedly created in source systems. To change this, the generation of the Stream XML rule has been enhanced such that at runtime it ignores optional nodes/attributes mapped to properties which do not exist or which have an empty value. NOTE: this new behavior in Stream XML rule generation is effective only with the below DSS configuration (to avoid backward compatibility issues ): Owning Ruleset : Pega-IntegrationEngine Purpose : StreamXML/DetectEmptyProperties Value : true
SR-119245 · Issue 178510
Local List now supports '+'
Resolved in Pega Version 7.1.8
The '+' character was not being supported in Local List. This was traced to the Ajax post request converting the '+' character to a space, and code has been added to preserve the '+' character.
SR-119246 · Issue 178467
Localization improved for Lithuania
Resolved in Pega Version 7.1.8
If the localization was set to Lithuania, using a property of type Date with a control pxDateTime and configuring its display mode to Dropdown Lists only allowed 'month' to be selected rather than the whole date. In addition, the three letter month abbreviations were ambiguous, using "Rug" for both Rugpjutis (August) and Rugsejis (September) rather than Rgp and Rgs. These issues have been fixed.
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.
SR-119444 · Issue 179227
Updated sorting and filtering icons to work with JAWS
Resolved in Pega Version 7.1.8
As filtering and sorting did not use labels, JAWS was not announcing icon names without labels. This resulted in JAWS not announcing the filter list, that a column was sortable, the presence of a filter icon, or whether a column was sorted ascending or descending. This was due to the "ARIA" attributes not being generated without PegaWAI ruleset1, and the system has been updated to enhance the accessibility.