INC-189622 · Issue 682098
Cleaned up references to deprecated property type
Resolved in Pega Version 8.7
While using the Pega API to update a case from one application to another, an error was generated indicating the system was unable to find a property definition of “caseTypeClass” in pyAddableWorkList of the workpage. All properties in the clipboard pages of the work page are validated during this update: in this case, the check was for the caseTypeClass property, which is no longer used but which was on the clipboard page. To resolve this error, all remaining references to property casetypeclass have been removed.
INC-190819 · Issue 681999
Wrapper added to set correct bulk transfer context
Resolved in Pega Version 8.7
Bulk transfer was not working as expected when transferring an assignment from a flow defined in data class. Investigation showed the bulk transfer UI was getting picked from work- class while the post processing was running under data class context: this has been resolved by creating a wrapper activity in baseclass to call the post processing activity Work- .
INC-191645 · Issue 679536
Updated FieldLevelAuditing logic for page comparison
Resolved in Pega Version 8.7
Optimistic locking was resulting in orphan assignments and the error "Error: Flow Not At Task, Error: Flow Removed". In addition, Get Next Work was causing duplicate Field Level Auditing records. This was traced to a missed use case in the logic used in pxFieldLevelAuditing where previousPage and PrimaryPage are compared to see whether they are equal or not, and has been resolved by adding one more condition to mark previousPage as null when the update date time or commit date time are not updated as part of processing.
INC-192979 · Issue 677696
Case creation and Save As performance improvements
Resolved in Pega Version 8.7
Performance improvements have been made to the getApplicationRuleSetList() function to avoid unnecessary and repetitive database calls.
INC-194429 · Issue 682882
Updated FieldLevelAuditing logic for page comparison
Resolved in Pega Version 8.7
Optimistic locking was resulting in orphan assignments and the error "Error: Flow Not At Task, Error: Flow Removed". In addition, Get Next Work was causing duplicate Field Level Auditing records. This was traced to a missed use case in the logic used in pxFieldLevelAuditing where previousPage and PrimaryPage are compared to see whether they are equal or not, and has been resolved by adding one more condition to mark previousPage as null when the update date time or commit date time are not updated as part of processing.
INC-194981 · Issue 681369
Validation error message corrected for delegated SLA rule
Resolved in Pega Version 8.7
When delegating any SLA rule to a Business user like the Manager Access group, editing it from the Case Manager portal did not give an option to configure seconds in that available text field (label hh:mm) even though the validation error stated that the time needed to be in hh:mm:ss format. The pzDelegatedSLAGoal, pzDelegatedSLADeadline and pzDelegatedSLAPassedDeadline sections do not include seconds field, which is a difference from Designer Studio (hh:mm:ss). For this update, the validation error message has been corrected to indicate only hh:mm is used while delegating the SLA rule. An enhancement is planned in a future version to support the hh:mm:ss format for this use.
INC-198514 · Issue 688852
CheckFlowDependencies query performance improved
Resolved in Pega Version 8.7
In order to improve performance on very large tables, the pxCheckFlowDependencies activity has been modified. Previously, checking whether a dependency exists retrieved all columns. The updated query will instead return a count.
INC-155624 · Issue 648057
MSGraph email listener enhancements
Resolved in Pega Version 8.7
Attachments with .eml /.msg extensions were treated as FileAttachments by the MS Graph API and generating a classcastexception. To resolve this, a check has been added to identify the attachment along with content type so .eml will be correctly recognized. In addition, the MSGraph email listener functionality related to converting from Graph to MIME message has been enhanced around the 'TO' and 'CC' recipients in a MIME message and for parsing nested attachments in Item attachment for addition to MsgraphMessage.
INC-156674 · Issue 661983
Handling added for reactivating combined Passivation and AccessGroup timeout
Resolved in Pega Version 8.7
Refreshing a passivated browser window in Dev Studio for an operator with a combined access group and passivation timeout was resulting in a blank screen after re-authenticating. InvalidParameterException and InvalidReferenceException messages were logged. Research showed this was caused by a missing pxPortal property on the pxThread page along with missing Application and Accessgroup pages. While refreshing the browser along with the top URL, there will be few requests with tab threads calling activities such as deletedocumentpg and SetProcessWindowName because there was an unload. Because these requests reached the server before re-authentication, the threads proceeded to the activation flow, causing properties such as pxPortal, Application, and Accessgroup pages to be removed from the thread page and requestor page according to the condition that the requestor was not yet authenticated. To resolve this, the logic in session.internal.authorization.context.BasicApplicationContextImmutableImpl#applyApplicationProperties has been updated to skip removing application page properties from the thread page in this combined Passivation and AccessGroup timeout scenario.
INC-159244 · Issue 627863
Bulk actions check in preserves declare expression legacy setting
Resolved in Pega Version 8.7
When a declare expression was saved in legacy mode with "Whenever used" selected in change tracking, performing a bulk check-in of the rule caused the expression to default to the new forward chaining method. This did not occur when using a direct check-in. Investigation showed this was caused by the check-in page holding a legacy value before the step execution, and has been resolved by adding a pre-save activity before the validation activity that will restore the .pyIsLegacy value from .pyExpressionTypeSelector, if set.