INC-155469 · Issue 616911
Attach Documents Control updated for busy indicator timing
Resolved in Pega Version 8.5.3
When using the standard control - Attach content - to attach documents for processing in the application, selecting multiple files for upload and then clicking on the attach button before the busy indicator started resulted in not all files being uploaded. Investigation showed that the busy indicator was not set to display as soon as the attachments were added, giving an opportunity to click "Attach" before all the documents could be successfully added to the process. As part of the resolution for this issue, the busy indicator will be displayed immediately upon file selection.
INC-153957 · Issue 615290
Cache key handling updated for OAuth2 Connect-REST
Resolved in Pega Version 8.5.3
After upgrade, a Connect-REST using OAuth2 credentials was failing with HTTP response code 403 when the Connect-REST was invoked by the agent, but the Connect-REST was successfully invoked from web node with the same Auth profile. OAuth2 tokens are stored in the cache and database. In this specific environment the key formation was happening differently on the utility node for batch processes, causing different keys to be formed for the same token. This has been resolved by adding a provider filter and updating the cache key.
INC-160288 · Issue 626068
Kerberos handling updated for database remap
Resolved in Pega Version 8.5.3
After upgrade from Pega v7.2 to Pega v8.4, using Kerberos authentication was failing during the remap task. Investigation showed that null username and password values were being passed to SchemaAssignmentUtility along with the flags as arguments, causing the utility to misinterpret the arguments. As arguments should be populated only when flags and values are available and not null, an update has been made which will set the username and password flags only if they are not null in the Remap database tables target.
INC-136659 · Issue 593767
Template circumstancing works for report definitions
Resolved in Pega Version 8.5.2
On circumstancing the pyMyCasesReport using the Template option, it always displayed the base report definition instead of the circumstanced one when referenced the same report in the table in section. Because the grid component called two activities 'pxRetrieveReportData' and 'pxRetrieveReportMetadata' to render the table, the step page passed to these activities was from @baseclass. This caused the circumstanced template created in work- class to not get picked up. To resolve this, updates have been made to ensure the step page to the above activities will be of the report definition class.
INC-160887 · Issue 629272
Resolved strategy optimization exception
Resolved in Pega Version 8.5.3
After upgrade from v8.2 to v8.5, Customer Decision Hub strategy failures were seen in the data join used with a datapage/page list to fetch some results. Errors appeared in the logs and UI. The exception indicated that the Strategy Parser for the new execution engine (SSA) was not able to parse and inline the used expression. Normally this exception would be caught in subsequent processing and the component where the exception is used would fall back to legacy so as to not affect the runtime behavior, but this scenario triggered a corner case inside the parsing logic for Data Join and Exclusion shape which caused the exception and stopped the process. To work around this issue, the Data Join configuration can be split into two shapes: create a new Data Import shape to only import the Page list, e.g. 'Page.pxResults', then on the original Data Join component, instead of joining the 'Page.pxResults', join with the new Data Import shape. This issue has been resolved by catching the exception when compiling the Data Join component and properly falling back to the Data Join shape.
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-157353 · Issue 624011
Handling added for autoclose of assignment in tabbed MDC
Resolved in Pega Version 8.5.3
After configuring an Ajax container in a section using tabs and max doc defined as 8 with 'doClose' set after processing has been completed, finishing the assignment caused the work item tab to stop working. Checking the console showed a script error was being thrown. Investigation showed that when the doClose action was triggered and tried to find the activeTabs in MDC, the target element being fired was null. This has been resolved by adding a condition for the doClose to handle the combination of autoclose and tabbed MDC that will close the current Ajax container div before proceeding.
INC-121480 · Issue 595824
EnableRedirects property added for REST connections
Resolved in Pega Version 8.5.3
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.
INC-127420 · Issue 568439
Requestor details shown in Pr_perf_stats table
Resolved in Pega Version 8.5.2
When using a Custom table with the requestor details inserted in the ApplicationSetup activity, comparing the passivated requestors from standard table Pr_perf_stats showed that sometimes requestor details were not present in table Pr_perf_stats. This was traced to the the column value for standard table being greater than the column value for the columns pxDecryptCount, pxDecryptCPU, pxDecryptElapsed, pxEncryptElapsed, pxEncryptCPU, and pxEncryptCount. Database numeric column size is (9,6) whereas other numeric columns have size (18,6). To resolve this, the table scripts have been modified to increase the column size from (9,6) to (18,6).