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-D30944 · Issue 503232
Corrected pagination alignment in tabbed layout sourced from RD
Resolved in Pega Version 8.2.4
Pagination numbers were not being presented inline with the next/back arrows when using a tabbed table layout with source:report definition. To resolve this, the pyGridPaginator function has been added to Pega-Gadgets in Work- .
INC-163644 · Issue 652968
Error message handling added for nested page lists
Resolved in Pega Version 8.7
When a multiselect referring pagelist(x).pagelist2() had an error message, the error was repeated for all pagelist(y).pagelist2() in the UI. This has been resolved by adding error handling for nested page lists by using registerErrorMessages for multiselect errors.
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.
INC-179175 · Issue 664046
Mobile barcode scan sets value with correct context
Resolved in Pega Version 8.6.2
After implementing a list of items where each has a unique barcode, scanning the barcodes using the mobile app worked correctly the first time but subsequent scans were setting the value on the first element of the list and missing the context of the current scan position. This has been resolved with an update to ensure the scan barcode action sets the value on the correct property when using repeating dynamic layers.
INC-179175 · Issue 664047
Mobile barcode scan sets value with correct context
Resolved in Pega Version 8.7
After implementing a list of items where each has a unique barcode, scanning the barcodes using the mobile app worked correctly the first time but subsequent scans were setting the value on the first element of the list and missing the context of the current scan position. This has been resolved with an update to ensure the scan barcode action sets the value on the correct property when using repeating dynamic layers.
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.
INC-187610 · Issue 672841
Logic made consistent for design time group condition
Resolved in Pega Version 8.7
An inconsistency was seen between the logic string that appears when switching from "Group ORs" mode to "Use advanced logic" mode at design time, though whichever mode was used at Action check-in was always properly reflected on the generated proposition filter so there was no runtime impact. This design time issue was traced to the property "pyGroupConditionsByOld " being empty: this property is transient so its value will not be saved into database. This property should be updated whenever user changes the Logic operator from the drop-down, and this has been resolved by adding an intermediate property to hold the old group condition value when it changes.