INC-174716 · Issue 656441
Updated handling for validating/saving circumstanced rule on branch
Resolved in Pega Version 8.7
Using 'save as' for an already circumstanced rule with a new property/template caused the Rule-.DictionaryValidation activity to register the error "StandardValidate-CircumPropAlreadyDefined". The same activity Step did not throw an error when saving into Branch. This was traced to the ruleset name not being the same for the branch ruleset due to having _BRANCH_Branch-Name appended to its name, and has been resolved by adding a condition to check for circumstanced rule in a branch.
INC-143461 · Issue 601838
Updated JSON DT nested page property handling
Resolved in Pega Version 8.5.2
In a JSON data transform, when using an "Update page" step on a single-page property, as a child step of an "Append and map to" step where a pagelist property is given, the pagelist was populated with only one result but the single-page property was treated like a pagelist and received multiple results. This has been resolved by updating the ClipboardJSONDeserializer implementation and downstream abstractions to support "clipboard only" relations as properties in nested PageLists.
INC-144978 · Issue 600590
Updated JSON DT nested page property handling
Resolved in Pega Version 8.5.2
In a JSON data transform, when using an "Update page" step on a single-page property, as a child step of an "Append and map to" step where a pagelist property is given, the pagelist was populated with only one result but the single-page property was treated like a pagelist and received multiple results. This has been resolved by updating the ClipboardJSONDeserializer implementation and downstream abstractions to support "clipboard only" relations as properties in nested PageLists.
INC-143461 · Issue 601840
Updated JSON DT nested page property handling
Resolved in Pega Version 8.6
In a JSON data transform, when using an "Update page" step on a single-page property, as a child step of an "Append and map to" step where a page list property is given, the page list was populated with only one result but the single-page property was treated like a page list and received multiple results. This has been resolved by updating the ClipboardJSONDeserializer implementation and downstream abstractions to support "clipboard only" relations as properties in nested Page Lists.
INC-144978 · Issue 600589
Updated JSON DT nested page property handling
Resolved in Pega Version 8.6
In a JSON data transform, when using an "Update page" step on a single-page property, as a child step of an "Append and map to" step where a page list property is given, the page list was populated with only one result but the single-page property was treated like a page list and received multiple results. This has been resolved by updating the ClipboardJSONDeserializer implementation and downstream abstractions to support "clipboard only" relations as properties in nested Page Lists.
INC-85182 · Issue 622326
Process added to clear unneeded requestors from shared pools
Resolved in Pega Version 8.6
Shared service requestor pools were persistently showing a growing count of active requestors when a service was under heavy use, potentially leading to timeouts and exceptions. Investigation showed requestors were moving from active to inactive without updating the pool manager, causing service requestor pools to be held in an inconsistent state with active requestor pools not going down even after completion of service request. To resolve this, a job scheduler process has been added to stabilize the service requestor pools heuristically.
INC-183728 · Issue 665133
Oracle handling updated for primary key in upgrade DDL
Resolved in Pega Version 8.7
Previously, when a primary key of a table was created Oracle would automatically create a unique index with the same name as the primary key. However, with the introduction of Oracle 19, an optimization was added which will not do that if there is another unique index on the table which contains the column(s) of the primary key. This difference can cause updates to fail with the error "cannot drop index used for enforcement of unique/primary key". This has been resolved by updating the handling for primary key constraint and the corresponding index name.
INC-139695 · Issue 593083
Mountain timezone format updated
Resolved in Pega Version 8.5.2
If an operator was created with any calendar instance timezone mapped to "Canada/Mountain" and made unavailable for the current period, routing an assignment to that operator using the standard ToCurrentOperator activity resulted in a null pointer error when the Rule-Utility-Function was executed to find a substitute operator. This was traced to the timezone format Input to DateTimeUtils API (parseDateTimeString) having the wrong timezone, for example, 20200819T080000.000 MDT (CA), and has been resolved by modifying the locale XMLs to remove (CA) from zone code so that MDT (CA) is updated as MDT.
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-125633 · Issue 589577
Oracle performance improvement
Resolved in Pega Version 8.5.2
Poor performance was seen when importing a RAP with schemas using Oracle. To resolve this, an update has been made which will set the Oracle tuning parameter at the session level by altering the setting "_OPTIMIZER_PUSH_PRED_COST_BASED"=false before the SMA query involving all_constraints. The setting will be returned to true after the execution of the SMA query. This is controlled through the prconfig setting '"database/performance/smaqueryperformanceenabled" which defaults to true so the setting and unsetting of the Oracle parameter is automatic.