SR-D6555 · Issue 457241
Access When check added for pyStartCase privilege
Resolved in Pega Version 8.1.6
If a privilege was defined in the pyStartCase flow rule and the access role to object assigned a privilege based on 'Access When' (not production level), the user was not able to start a case. This was traced to the havePrivileges RUF passing an incorrect primary page to evaluate the privileges in combination with the 'access when'. To resolve this, the engine API will call tools.getAuthorizationHandle().havePrivilege for each privilege until it finds a match.
SR-D12511 · Issue 484664
Corrected error when resolving subcase from Review harness
Resolved in Pega Version 8.1.6
An error occurred when resolving a subcase if it was opened from the review harness. It was possible to resolve the subcase successfully if the local action was invoked from the Perform harness. Investigation showed that the update status was called twice, once from pyForcecaseclose and again from the update status of the activity. This has been resolved.
SR-D15154 · Issue 488069
CaseType picks up stage name correctly
Resolved in Pega Version 8.1.6
When adding a new stage in the Stages tab of a case type (pyDefault rule), the stages were shown as rule name instead label after saving and at runtime. Directly adding the Stages in the 'Workflow' tab of the case type showed the stage label as expected. This was traced to an issue with the current row of the table not being properly refreshed, leading to old data being submitted while saving. This has been resolved by adding an explicit "refresh current row" configuration on pyStageName under primary and alternate stage table layouts.
SR-D15216 · Issue 487680
Email parameter handling updated for greater backwards compatibility
Resolved in Pega Version 8.1.6
After a major migration, email failures were seen with the message "Error sending email: To Address not available". This was traced to a difference in handling between the old and new system versions for fetching the details of workparty for the ToParty parameter, and has been resolved by modifying the newer Work-.pzGetEmailFromParty and Work-.pzSendEmail activities to handle party role as well for greater backwards compatibility.
SR-D17973 · Issue 489740
Corected parameter mismatch to allow deletes to be added to history
Resolved in Pega Version 8.1.6
Pega was not keeping track of a property if it was deleted from the data explorer tab, resulting in not being able to restore the deleted property. This was traced to a parameter mismatch: the Delete API adds the Memo parameter to the history, but while DeleteRecord accepted the Memo parameter, DeleteRecordInner accepted the HistoryMemo parameter. Because the parameters names were different, they were not propagated to the API. This has been corrected by setting the param.memo so that Rule-Delete API adds the history and the rule gets displayed correctly in recently deleted rules.
SR-D211 · Issue 481397
Case Assignment issue lock corrected
Resolved in Pega Version 8.1.6
After upgrade, an intermittent error was seen when browsing the screen flows of a child case type application, indicating "Users have lost the ability to make this change because a change elsewhere has taken precedence over the change you made here. Please click on the assignment again to continue". This was traced to a change made to address an issue with the Opener not properly honoring the aUnlockOnCommit flag that was passed in via the openIfStale() API: in a very specific use case following that change, the system would unlock work objects during openIfStale when it should not. This has been corrected.
SR-D3929 · Issue 444529
Auditing for automatic stage transitions improved
Resolved in Pega Version 8.1.6
The logic for pzCheckForAndDoAutomaticStageTransition has been updated to provide better audits for the movements related to automatic stage transitions.
SR-D22601 · Issue 499898
Fixed PEGA0069 alerts with Weblogic
Resolved in Pega Version 8.1.6
When Pega platform was deployed in a Weblogic application server, Alert PEGA0069 was not generated due to the cookie parser failing to parse what was found to be an incorrect Pega-Perf cookie value. The Pega-Perf cookie value has been corrected by removing quote characters surrounding it.
SR-D800 · Issue 487308
Mashup error resolved with try/catch block for Microsoft Internet Explorer framelement exception
Resolved in Pega Version 8.1.6
When a portal was launched using mash up, the intent tasks were not launched in Microsoft Internet Explorer when Add tasks button was clicked. This was found to be a site-specific use case only found with IE, and has been resolved by adding a try catch block for a window.framelement exception thrown by IE.
SR-D19625 · Issue 494822
Handling added to chart drilldown for apostrophe in operator name
Resolved in Pega Version 8.1.6
Chart drilldown was not working if the operator name contained an apostrophe. Handling for this has been added.