SR-A9198 · Issue 218533
Text retrieval for deprecated "Query" button updated for universal browser support
Resolved in Pega Version 7.2
The Firefox popup window provided by the Product rule when querying "Individual Instances to Include" failed to transpose the selected rule information back into the Product ruleform when the OK button was clicked. This was due to the use of the deprecated "Query" button, which does not have support for all browsers, to launch the ListView. To handle this, the node text retrieval method in DataInstancesQueryScript has been updated to use the 'textContent' function (compatible with all browsers) instead of the previous 'innerText'.
SR-A10839 · Issue 222017
Added handling for null rollback info in hotfix autocommit
Resolved in Pega Version 7.2
If AutoCommit was selected while installing a hotfix, the auto-commit would fail and leave the hotfix in an Uncommitted state if there were dependent hotfixes where changes were covered by the parent and the child was superseded after installing the parent. Manual commitment of the hotfix worked as expected. This was an edge case where the older hotfix did not get rollback information saved since its components were already installed or superseded, and AutoCommit has been updated to handle this missing information.
SR-A10327 · Issue 222830
Upgrade Assistant enhanced to better resume interrupted process
Resolved in Pega Version 7.2
If the system suffered a crash during upgrade, IUA was incorrectly identifying the DB as having completed the upgrade and would import outstanding rules based on the perceived Database BLOB version. This led to a storage-type mismatch between Prod and all lower environments, and BIX jobs would fail due to not being upgraded. An enhancement has been added to the Upgrade Assistant to correctly resume an interrupted upgrade process.
SR-A12287 · Issue 223279
Alter Script generates correct SQL for Oracle db
Resolved in Pega Version 7.2
During installation, an incorrect Alter Script was being generated while importing the JAR file due to a missing check on the 'required' XML attribute for dbtype Oracle to decide whether it should be null or not null. This has been corrected to honor the 'required' attribute and accordingly the generated SQL will be appended with null/not null string.
SR-A12687 · Issue 226506
Skimming logic corrected
Resolved in Pega Version 7.2
The skimming logic (PegaRULESMove_Skimming_Query) has been updated to correctly repopulate the query page in order to return a more accurate rules count.
SR-A2733 · Issue 220049
Migration process handles underlying varchar CHAR
Resolved in Pega Version 7.2
Handling for CHAR length semantics has been added for imports of rule schema to support Oracle varchar2 columns, and the import/export will correctly deal with the circumstanced columns of CASETYPEVERSION and PXREFOBJECTCLASS.
INC-145293 · Issue 610935
Additional diagnostic logging added for ElasticSearch startup issues
Resolved in Pega Version 8.5.6
The PyIndexerState was stuck in Starting status during node initialization. This issue could occur if the filesystem became hung due to network level issue while scanning entries from /etc/mtab, resulting in a lock which was not released correctly. In order to better determine which node entry in a cluster may be responsible for the hang, an update has been made which will use a temporary virtual environment to repeat the part of the initialization phase responsible and generate additional logs for debugging. To activate this, the PegaSearch.Diagnostics logger must be set in DEBUG mode. This duplicated virtual initialization will not interrupt the normal initialization.
INC-163791 · Issue 666195
Simplified default reference time calculations
Resolved in Pega Version 8.5.6
After a job scheduler was configured to run at Start time = 21:00:00 for Time zone = Europe/London, the scheduler determined 20:00:00 as the next start time. This was due to the calculation for the next start time using the time zone offset calculation pattern for the date and time stored in System-Runtime-Context.pxCreateDateTime, which had difficulty with changes to the time zone definition implemented in the time between the given date and today (meaning the current time) such as daylight savings time. To resolve this, the default reference time from System Runtime Context will be 'now' instead of Date(0).
INC-168253 · Issue 660882
Documentation updated for using Connect MQ with clustered queues
Resolved in Pega Version 8.5.6
After update to Pega Platform v8.6, an issue was seen with Connect MQ rules that used an alias queue. The support documentation has been revised to outline the necessary steps for updating an application to perform as expected. In the Pega-IntegrationEngine ruleset, create the following dynamic system settings and their default values: "mq/pmo" = 0 "mq/gmo" = 0 "mq/oo_request" = 1040 "mq/oo_response" = 16 For more information, dynamic system setting support articles are available.
INC-174625 · Issue 655241
Admin Studio will consider cluster protocol when returning listener status
Resolved in Pega Version 8.5.6
When using a few nodes in standalone mode for BIX extract combined with server nodes using Hazelcast, opening the admin studio pages with service discovery caused an error to be thrown. This was traced to the system writing an entry to pr_sys_statusnodes table as an embedded node whenever a BIX extract was triggered, causing those standalone nodes to be incorrectly considered by the listener landing page. This has been resolved by configuring the system to either return the local member when the cluster protocol is standalone or to return all Hazelcast members if the cluster protocol is Hazelcast.