SR- · Issue 404593
Thread name implementation fixed for FCM use with micro DC
Resolved in Pega Version 8.1.1
When attempting to invoke a remote case in the Interaction Manager portal via FCM with the Customer Service for Insurance application which uses micro DC, the case was not invoked and an empty screen was displayed. Invoking the case from the interaction portal resulted in a JavaScript error. Invoking the case from a WSS or directly from the Create button in Designer Studio worked correctly. This was traced to a recent change to the implementation for generating the thread name. Because of this, CRM apps could not load the Federated cases via micro DC. This has been fixed through changes in "pzFCMMashupGadget" to replace the slash with underscore for the FCM thread.
SR- · Issue 406436
OIDC and authorization_code flow corrected
Resolved in Pega Version 8.1.1
The OIDC and authorization_code flow was not working work on the first attempt. This was traced to the server that was performing the OAuth 2.0 authorization_code redirecting straight to the Pega application after successful user authentication instead of returning an authorization code via redirect_uri. As a result, the Pega application was rendered in a external Safari window which is supposed to be used for user authentication only. Second and subsequent attempts to perform the OAuth 2.0 authorization_code flow were successful and the Mobile Client was logged in. This was caused by the unnecessary retainment of state parameters in the OIDC flow, and has been fixed by removing the code that appended the querystring parameters used for the Hybrid Client.
SR- · Issue 402877
Merge Wizard errors fixed, and created rules will use the highest ruleset version available
Resolved in Pega Version 8.1.1
Code errors in the Merge Wizard that were causing Null Pointer Exception errors have been fixed, In addition, branch rule sets created through this wizard did not have the 'Application validation' option and rule set pre-requisite filled automatically; the system has been updated so the version prerequisite will be the highest existing ruleset version in the ruleset.
SR-103429 · Issue 136984
Rule-Service-Java authentication in a stateless session re-enabled
Resolved in Pega Version 7.1.7
When exposing Rule-Service-Java through a service package, a proxy jar file is created. If the 'Requires Authentication' option was checked on the service package, the generated java did not contain the required code to pass through the username/password and authentication failed. This method of passing credentials via proxy method parameters was previously withdrawn for the stateless processing mode, but the java code has been reinstated to enable authentication for a stateless session if this method is desired.
SR-106939 · Issue 176612
Added support for skipping explicit validation in tabbed screen flow
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When using a tabbed screen flow harness in the application and uploading a file using the "FilePath" control, there is a check in the post activity of the flow action of the first screen to see if the user has browsed a file. When the user proceeds to the next screen by clicking 'next', the file is validated and attached to the work object. However, if instead of clicking on the Next button the user clicked on the tab to go to the next screen, the validation failed and the file was not attached. This problem was traced to the 'GoToPreviousTask' activity failing to pass the parameter page in this scenario, and has been fixed by adding a new step to update the existing parameter page with necessary parameters to allow validation and attachment when skipping the 'next' button.
SR-108009 · Issue 154664
Execution plan reuse on SQL Server 2008 R2
Resolved in Pega Version 7.1.7
Due to the way a SQL server treats execution plans, each decimal bind value with a different scale is treated as a different type. To optimize the execution, the scale value for the execution plans will now be set the same as the table definition for obj- methods.
SR-108346 · Issue 166436
Corrected purging for History and Attachments
Resolved in Pega Version 7.1.7
A problem was found with purging the History and Attachments for cover and folder items. This was traced to history tables using datetime columns as key properties: many databases round these values to less precision than PRPC uses, and the keys did not match. The purgeitems function has been updated to delete the instance specifically and bypass recalculating the InsKey.
SR-108805 · Issue 149539
Help updated to explain When Rule "ALL" Evaluation behavior
Resolved in Pega Version 7.1.7
A 'when' rule evaluating all pages in page list will only evaluate the properties on pages in the list that contain that property. This may cause a "true" result that does not match customer expectations. The hover help has been clarified to explicitly state that the evaluation results apply only for those pagelist entries where the property exists and not for all the page list entries.
SR-108838 · Issue 154989
Increased limit for Rule_Obj_CaseType
Resolved in Pega Version 7.1.7
Previously, Rule_Obj_CaseType was encountering a byte limit of 65535 in the JVM that impeded the ability to create a desired large number of coverable work types (54+). The system code has been modified to store the rule types differently to avoid generating extra lines of java code for each coverable case type.
SR-109455 · Issue 172370
CSS generation fixed for attaching files after validation failure
Resolved in Pega Version 7.1.7
After a validation had failed, uploading a file (through the filePath Control) and submitting the flow action resulted in the page loading with no CSS applied. This has been corrected by changing how the uploading wrapper is applied in cases of validation failure.