INC-211480 · Issue 712419
Handling added updates involving Oracle descending column
Resolved in Pega Version 8.6.4
The build was failing when attempting to update to Pega 8.6, and an error indicating an issue with Oracle columns was generated. Investigation showed that when a column changed that belonged to an index which had a 'desc' column (even if the changed column was not specified as desc), an Oracle restriction was triggered. This occurred with any column size increase if the column participated in an index containing a descending column or a function index. This has been resolved by adding a step to drop the index before altering the column if a Descending index is involved, and to catch the case where the resized index is part of an index that has a descending column but is not necessarily a descending column itself.
INC-211480 · Issue 712418
Handling added updates involving Oracle descending column
Resolved in Pega Version 8.7.2
The build was failing when attempting to update to Pega 8.6, and an error indicating an issue with Oracle columns was generated. Investigation showed that when a column changed that belonged to an index which had a 'desc' column (even if the changed column was not specified as desc), an Oracle restriction was triggered. This occurred with any column size increase if the column participated in an index containing a descending column or a function index. This has been resolved by adding a step to drop the index before altering the column if a Descending index is involved, and to catch the case where the resized index is part of an index that has a descending column but is not necessarily a descending column itself.
INC-211480 · Issue 712420
Handling added updates involving Oracle descending column
Resolved in Pega Version 8.8
The build was failing when attempting to update to Pega 8.6, and an error indicating an issue with Oracle columns was generated. Investigation showed that when a column changed that belonged to an index which had a 'desc' column (even if the changed column was not specified as desc), an Oracle restriction was triggered. This occurred with any column size increase if the column participated in an index containing a descending column or a function index. This has been resolved by adding a step to drop the index before altering the column if a Descending index is involved, and to catch the case where the resized index is part of an index that has a descending column but is not necessarily a descending column itself.
INC-234543 · Issue 743003
Parameter value with carriage return evaluated correctly
Resolved in Pega Version 8.8
If a text area control had multiple lines entered in it and the same text area was passed as a parameter to a Data Transform executed at the launch of a read-only harness, the value in the text area was - " #~pyworkpage.propertyname". If the text area had just a single line without any enters/multiple lines, then it worked as expected. This was traced to the handling in pzpega_ui_events and has been resolved by escaping the newline and carriage return characters. An additional issue found when using multiselect in the form was traced to the correctActionArgs function which was generating the replacedtoken "//string//" for one of the property subjectareadetails, and this has been corrected.
SR-D65327 · Issue 534571
Backspace keydown handler updated for all textinput modes
Resolved in Pega Version 8.5
Attempting to use the Backspace key to remove input from a number cell (either Integer or Decimal) did not work. When the action was performed by a Manager, the Backspace key works as expected. Investigation showed the logic in the keydown handler for the backspace key in pega_report_events.js was only ignoring the e.preventDefault() call when the textinput node type was text, not number or other input types. To correct this, the keydown handler has been updated so the backspace key in pega_report_events.js maintains the default backspace functionality for all textinput modes, not just those of type 'text'.
SR-119538 · Issue 177397
Detection added for custom work history tables
Resolved in Pega Version 7.1.7
In order to fully embrace mobile capabilities, columns were added to the work history tables to allow actions to be tracked as a geographical map where each history event is a numbered locale indicator on a map instead of a row of entries. From lat/long it is also possible to call a Google service and get the street address as well. However, this functionality caused some issues post-migration with if there were customized pc_history_work tables mapped to custom classes. To remedy this, a check has been added to only query for pxlatitude/pxlongitude if columns are exposed and shown, and that will detect if the columns aren't present.
SR-133561 · Issue 203840
Garbage Collector tool removed from SMA
Resolved in Pega Version 7.1.9
Issues were found when attempting to view Garbage Collector statistics in SMA, and the "Collect" button which should point to the GC log instead gave an error. After investigation, it has been determined that the SMA Garbage Collector Tool no longer meets customer needs: it failed to parse JDK 1.7 GC logs and did not give useful failure information when parsing a JDK 1.6 log. Therefore, the Garbage Collector function has been removed from the system. Instead, third-party analysis tools such as HP Jmeter and IBM Support Assistant are recommended for this purpose.
SR-A12345 · Issue 224099
Improved visibility for roles associated with objects
Resolved in Pega Version 7.2
Issues were encountered while attempting to access roles associated with objects on the access role name rule form if 'Rule-Access-Deny-Obj' was used. Not all of the ARO and ADO definitions for the Access role were visible and the error "Failed to find a 'RULE-OBJ-FLOWACTION' with the name 'PZADDMODIFYROLE' that applies to" was generated. This has been corrected by adding and updating the required rules to support displaying both Access role objects and access deny objects on access role name rule form: the grid will be updated to display both RARO and RADO, but to simplify, the add-a-row functionality at the bottom will be limited to RAROs only.
SR-A8289 · Issue 218291
Improved visibility for roles associated with objects
Resolved in Pega Version 7.2
Issues were encountered while attempting to access roles associated with objects on the access role name rule form if 'Rule-Access-Deny-Obj' was used. Not all of the ARO and ADO definitions for the Access role were visible and the error "Failed to find a 'RULE-OBJ-FLOWACTION' with the name 'PZADDMODIFYROLE' that applies to" was generated. This has been corrected by adding and updating the required rules to support displaying both Access role objects and access deny objects on access role name rule form: the grid will be updated to display both RARO and RADO, but to simplify, the add-a-row functionality at the bottom will be limited to RAROs only.
SR-A88481 · Issue 256518
VBS starts with DDS configured to use external Cassandra
Resolved in Pega Version 7.2.2
If DDS is configured with Internal Cassandra which is then switched to External, DDS reports to be in state NORMAL and VBD can start. However, when starting from scratch with DDS configured to use External Cassandra, DDS was failing validation and reporting to be in state CLIENT, so VBD was unable to start due to VBD's check that ensures at least one DDS is in the NORMAL state before starting. To address this, the validation code that checks the DDS state when VBD is starting has been removed and the system will instead rely on the DSM service layer to ensure that DDS is functional before VBD can start.