SR-C74650 · Issue 422909
Grid alignment and headers corrected for Opportunities screen in RTL locale
Resolved in Pega Version 8.1.4
When using the RTL locale, the Opportunity detail screen and search screen had grid alignment and header issues. This has been resolved by updating the py-portal-stages css attached to the enduser skin.
SR-C74652 · Issue 422903
Grid alignment and headers corrected for Opportunities screen in RTL locale
Resolved in Pega Version 8.1.4
When using the RTL locale, the Opportunity detail screen and search screen had grid alignment and header issues. This has been resolved by updating the py-portal-stages css attached to the enduser skin.
SR-C83615 · Issue 424947
Support added for hiding unwanted category reports
Resolved in Pega Version 8.1.4
After upgrade, a customization used to hide unwanted out-of-the-box category reports was not working. This was due to the pyServiceLevelPerformance and pxSimulations category rules not being included as part of the pyOOTBVisibleInBrowser 'when' rule that is specified for Display in the report browser 'when' setting. These two category rules - pxSimulations and pyServiceLevelPerformance - have now been modified to reference the 'when' rule pyOOTBVisibleInBrowser so categories may be hidden as desired.
SR-B69595 · Issue 317880
Fixed UnsupportedOperationException from decision table
Resolved in Pega Version 7.3.1
When using embedded properties (e.g. .OfferData.Action) within a decision table, an UnsupportedOperationException appeared on the DSMClipboardProperty if it was executed via a Strategy rule. The issue was with a function being not implemented within DSMClipboardPage, and has been fixed.
SR-B51989 · Issue 310393
TimeStamp column includes milliseconds in extract
Resolved in Pega Version 7.3.1
Extraction to database output format was not showing the millisecond part of the datetime column. This was a missed use case for BIX when the support of Datetime property mapping to timestamp column was introduced in Oracle, and has been fixed.
SR-B68425 · Issue 317712
Text input focus corrected for repeating dynamic layout
Resolved in Pega Version 7.3.1
Clicking on the label of a text input for the second section in a repeating dynamic layout shifted focus to the first section's text input. This was caused by a missing repeating index for the attribute of the label when used in a RDL and has been fixed.
SR-B68425 · Issue 319425
Text input focus corrected for repeating dynamic layout
Resolved in Pega Version 7.3.1
Clicking on the label of a text input for the second section in a repeating dynamic layout shifted focus to the first section's text input. This was caused by a missing repeating index for the attribute of the label when used in a RDL and has been fixed.
SR-B56367 · Issue 313698
Query updated for Oracle DDL generation
Resolved in Pega Version 7.3.1
When using a class mapped to an external database view, creating a RAP that included a Data-Admin-DB-Table instance in a lower environment for import into a higher environment resulted in invalid generated DDL for the view. This was due to a column alias list in the view definition not being included in the generated DDL, and has been fixed by using a different metadata query for Oracle to ensure the column list is returned if it was originally specified.
SR-B67316 · Issue 317299
Query updated for Oracle DDL generation
Resolved in Pega Version 7.3.1
When using a class mapped to an external database view, creating a RAP that included a Data-Admin-DB-Table instance in a lower environment for import into a higher environment resulted in invalid generated DDL for the view. This was due to a column alias list in the view definition not being included in the generated DDL, and has been fixed by using a different metadata query for Oracle to ensure the column list is returned if it was originally specified.
SR-B53073 · Issue 313234
Handling fixed for properties with a leading dot
Resolved in Pega Version 7.3.1
Inconsistencies were seen in working with properties across different browsers: 1. If a field was set as requiring entering a property, pressing the arrow down to select the first value (i.e. topmost Page Name) caused the focus to point to the icon to the right of the control in Microsoft Internet Explorer and Google Chrome. 2. If it was not a required field, the focus was kept and the property could be set without using the mouse to reposition the focus to the field when in Microsoft Internet Explorer or Firefox, but only after HF was installed in Google Chrome and not for Autocomplete control. 3. When configuring Autocomplete control, the 'dot' disappeared when entering property names of embedded pages from the report based on exposed property when using Microsoft Internet Explorer, or if HF was installed in Google Chrome. This was found to be an issue where the non-required fields having a dot as prefix were having that starting dot trimmed off. To fix this, a check for extra dots has been added before trimming.