SR-B57228 · Issue 325976
Timer exit error fixed for STS SOAP
Resolved in Pega Version 7.3.1
If STS was enabled for a SOAP Connector and if a valid STS token was already available, hundreds of error messages about attempting to stop the timer were logged. This was traced to a step order error which started the timer and then exited before stopping it, and the missing step has been added.
SR-B70379 · Issue 326388
Post-printing screenshot window freeze fixed
Resolved in Pega Version 7.3.1
When an attached screenshot was clicked open and displayed in a pop-up window, the window was freezing after a print operation was performed. This was an issue with closing the ActiveX control through Microsoft Internet Explorer. To resolve this, the ActiveX control previously used has been changed to Silverlight.
SR-B65469 · Issue 330983
Connect-SQL documentation updated to clarify no milliseconds in Oracle TIMESTAMP
Resolved in Pega Version 7.3.1
The documentation for Connect-SQL rules has been updated to clarify that the datetime hint in rdb-save will not store millisecond precision in the TIMESTAMP column type of an Oracle database.
SR-B77020 · Issue 326989
Help file update to clarify Precondition exceptions do not have error handling
Resolved in Pega Version 7.3.1
The rule-/rule-obj-/rule-obj-activity/stepstransition help file documentation has been corrected to indicate the Exception handling does not cover any conditions that might occur in the precondition.
SR-B15150 · Issue 286741
Online help updated with current reindexing utility information
Resolved in Pega Version 7.3.1
The online help files have been updated to remove references to deprecated activities for reindexing declarative indexes. Information has been added for the currently supported utility, the column populator tool (prpcUtils or prpcServiceUtils) with expose option and 'expose.reindex=true', that specifically regenerates declarative index content.
INC-107737 · Issue 544662
Oracle handling updated for upgrade DDL
Resolved in Pega Version 8.6
DDL generated for a Pega upgrade displayed the error "ALTER TABLE PC_ASSIGN_WORKBASKET DROP CONSTRAINT GETNEXTWORKINWORKGROUP" when trying to install. This was traced to a change made by Oracle for optimization, and has been resolved by updating the handling for primary key constraint and the corresponding index name.
INC-121480 · Issue 595823
EnableRedirects property added for REST connections
Resolved in Pega Version 8.6
When implementing a connector with the header “Location” which contains a redirect URI, a 303 response code was expected. Instead, a 400 or 404 error was generated. It was not possible for developers to process the code per their logic in Activity as Connect REST processed 303 responses automatically - i.e. there was no intercept points to implement the suggested approach. To resolve this, the new property "Rule-Connect-REST.pyEnableRedirects" has been added along with a checkbox for the property in "Rule-Connect-REST.pyService" in "Connection" section. Logic has been added in RESTConnector.java to take value of this property and set it on the HTTPClient being used, and a method has been added to HTTPClient interface and ComponentsHTTPClient to use the new value being passed. The default behavior is the same for the REST Connector, but a client can uncheck a checkbox on the REST Connector ruleform to stop the HTTP client from automatically following any compatible 3xx responses.
INC-122112 · Issue 599792
Updated SLA table clearance
Resolved in Pega Version 8.6
After cases were resolved, SLA entries were not getting cleared from the SLA table. This caused the SLA table to have a huge number of Overall SLA and PendFlow details present for cases that were resolved or moved to the next state, which impacted case processing via SLA Agent. This was traced to SLA queue-items not being removed by delete-deferred as expected, and has been resolved by invalidating the deferred operations and scheduling item removal.
INC-125258 · Issue 601606
Documentation updated for troubleshooting rules counts
Resolved in Pega Version 8.6
The troubleshooting documentation has been updated with extended information regarding correcting incorrect rule counts in dashboards and reports.https://community.pega.com/knowledgebase/articles/pega-platform-troubleshooting/troubleshooting-incorrect-count-rules-dashboards-and-reports
INC-125633 · Issue 589578
Optimizing helper class enhanced to handle external databases
Resolved in Pega Version 8.6
Running a BIX extract that included a manifest for a target database was resulting in a null pointer exception for the manifest extraction. Attempting to generate the DDL for the manifest table also failed. This was traced to an issue with the helper class using a hardcoded default database for forming the queries, causing it to ignore the database config/DADN/prconfig for the Oracle database and form a query using the PegaRules' database credentials. This only occurred when trying to do external database operations on a different database platform; Oracle PegaRules worked as expected with an Oracle external database and Postgres Pegarules worked with a Postgres external database, but mixing Postgres PegaRules and an Oracle external database would result in the null pointer exception. To resolve this, the helper class has been enhanced to work with external databases by passing the database name as a parameter so it will properly calculate the query based on the type of target. An error in the name of the class has also been corrected, and is now available as PerformanceHelper rather than the previous "PerformaneHelper".