SR-C59062 · Issue 402917
Human and robot assignments workflow access differentiated and separated
Resolved in Pega Version 8.1.1
Previously, the "Access When" rule did not differentiate between human or robotic operator and each was able to work on assignments intended for the other. When a case was routed to a robotic work queue (and also when the robot VM had already picked up the work and was processing it), the assignment could still be picked up from the Review Harness and moved downstream by a human operator. To resolve this, the property pxAssigneeType has been created in AddAssign (Workbasket and Work List) to hold information about whether it is a human or robotic assignment, and canPerform(Work List & WorkBasket) has been modified to account for the operator type and assignment type. The error "You are not authorized to perform this assignment." will appear when an assignment routed to a robotic queue is accessed by a human. However, if the access group is administrator, the human operator can still progress the robotic assignment without any error.
SR-C59391 · Issue 402863
Handling added for work cases being synchronized after missing flow rule changes while offline
Resolved in Pega Version 8.1.1
Mobile application work items submitted offline did not always appear when online again.After coming back online, new work items that were created online were synchronized, but the work items that were created offline were not synchronized. This occurred when changes were made to the flow rule after cases had already been created offline. To resolve this, any failure in finishAssignment/ previousAssignment/ doSave actions which does PRocessAssignment will persist the incoming data from device in following way: 1. Create a Pega-Work-OfflineSync case. 2. Merge all the actions related to the failure work object and copy the merged page in pySyncErrorCase page. 3. If a work basket is configured, the newly created case is moved to the work basket else it is moved to the default work basket. To check the data please check the work basket or instances of Pega-Work-OfflineSync.
SR-C60129 · Issue 402896
Removed default height from pzTimeline_PresentationTab
Resolved in Pega Version 8.1.1
When using Timeline Control, the Default Height in the presentation tab was not being removed when it was changed to be blank and saved. When the control was opened the next time, it defaulted to show Height 300px and remained at that value despite repeated attempts to blank it. This was traced to a default height in the "pzTimeline_PresentationTab" section, and this default has now been removed.
SR-C60129 · Issue 402902
Removed default height from pzTimeline_PresentationTab
Resolved in Pega Version 8.1.1
When using Timeline Control, the Default Height in the presentation tab was not being removed when it was changed to be blank and saved. When the control was opened the next time, it defaulted to show Height 300px and remained at that value despite repeated attempts to blank it. This was traced to a default height in the "pzTimeline_PresentationTab" section, and this default has now been removed.
SR-C60591 · Issue 402938
Spring Framework updated to latest version
Resolved in Pega Version 8.1.1
In order to provide improved security, Spring framework has been updated to v.4.3.19.
SR-C60612 · Issue 402878
Modified "What's New" widget to remove use of webGL and improve browser performance
Resolved in Pega Version 8.1.1
The "What's New" widget on the Designer Studio home page was using WebGL to render its background animation. If the browser was running on a virtual machine without hardware acceleration, this widget could cause the browser to become unresponsive. While there was a workaround of using the 'Click the Hide this until next release' button to remove the widget for subsequent logins, the "What's New" function has now been modified to not use webGL.
SR-C61277 · Issue 402944
GRS values supported for pxTestEmailConnectivity activity
Resolved in Pega Version 8.1.1
After upgrade, the global parameter reference did not work in email accounts. This was an unintended consequence of recent email refactoring: although GRS values were being resolved in the activity and shown in the components tested section of the test connectivity gadget, they were not being passed to the pxTestEmailConnectivity activity. This caused the test connectivity to fail if the inputs configured in email accounts were in GRS syntax. To fix this, the SMTPConnectivity and POPorIMAPConnectivity activities of Data-EmailAccount class have been modified to add the GRS resolved values to an emailAccountPage which is passed as parameter to pxTestEmailConnectivity activity.
SR-C61479 · Issue 405988
Bix extract performance improved by only checking cipher type for encrypted properties
Resolved in Pega Version 8.1.1
Previously, if no cipher was configured in extract Rules the cipher type defaulted to null and wasn't cached. This caused performance issues when running against the database. In order to improve performance, the code has been modified to only check for cipher type if the property is encrypted.
SR-C61596 · Issue 402901
Fixed escaping of double quotes in UI control Tooltips
Resolved in Pega Version 8.1.1
Adding a tooltip to a UI control (such as a button) where the tooltip had both text in "double quotes" and outEx: foo "bar" baz caused a compile time error due to the double quotes not being escaped correctly. This has been resolved by using StringUtils.crossScriptingFilter at design time in pzGenerateLinkOrButton for non template and {{{}}} (triple braces) for template.
SR-C62405 · Issue 402960
Check added to resolve privilege error on RAP import
Resolved in Pega Version 8.1.1
Importing a RAP file containing a circumstances rule to alter the table "pr_index_circumstance_def table" was giving an "insufficient privileges" error if the user did not have the privilege to alter the table. Each time a circumstanced rule is created, it attempts to not only insert an instance into the index table but also tries to expose a new column matching the circumstanced property. Given this, creating a circumstanced rule ultimately required access to modify database schema. To resolve this, a check for DASS AutodatabaseSchemaChanges has been added, and the system will bypass making schema changes in saveCircumstanceIndex activity if same is set to false.