SR-D13533 · Issue 488346
Grid generation updated to facilitate button with on-click action
Resolved in Pega Version 8.1.6
An issue with an on-click event not getting fired was traced to an issue with Action generation on a button in a grid cell. This has been corrected by removing the code that set the parameter "isTemplatizedGrid" in runtime during grid generation.
SR-D21266 · Issue 489799
Corrected mathematical operations in mobile offline data transforms
Resolved in Pega Version 8.1.6
Mathematical operations such as *, /, or % were not working in mobile offline data transforms. This has been corrected by updating pzpega_ui_datatransform_generator.js to support all mathematical operations and actions.
SR-D6947 · Issue 444603
Email AttachmentPage updated to support use of Data-WorkAttach
Resolved in Pega Version 8.1.6
Attachments were not getting appended in the email sent by the Agent SendCorr. This was traced to a null Page that resulted if the attachment was of type custom Data-WorkAttach, and has been resolved by modifying the condition check on the objclass of AttachmentPage to change it from equalsIgnoreCase(Data-WorkAttach-File to startsWith(Data-Work-Attach-) .
SR-D6261 · Issue 486482
Enhancement added to support mobile offline multiple assignments for single workitem
Resolved in Pega Version 8.1.6
After completing stage1 of creation, a case generated two assignments intended for another user. That user was then unable to open the screenflow assignment in mobile offline. Investigation showed that the system was using one--to-one mapping of a workitem to assignments for offline. If multiple assignments were created for the same work object, only the first one was packaged. Changes have now been added to support more than one assignment for single workitem.
SR-D18217 · Issue 489811
Corrected PDF generation when an image filename has special characters
Resolved in Pega Version 8.1.6
When using Export to PDF with an uploaded image file that had special characters in its name, the images were missing from the generated document. This has been corrected by updating the decoding of the URL to not remove the checksum when using RTE.
SR-D27644 · Issue 497613
Uploaded attachments will receive a unique name to prevent overwriting
Resolved in Pega Version 8.1.6
An issue with an incorrect file being attached to a work object was traced to overlapping processes. When files are uploaded, they are first saved to common HDD directory and then read into memory and deleted from the HDD area. Files will overwrite other file carrying the same name, which is a problem if the first file is not completely uploaded and is waiting in the common directory and some other file with the same name is uploaded on top of it. To resolve this, an update has been made to ensure file names are appended with a unique identifier to distinguish between files carrying the same names and keep them from overwriting each other.
SR-D15262 · Issue 486889
GetNextWork properly switches applications for 'most urgent'
Resolved in Pega Version 8.1.6
Post upgrade, the "Get most urgent" button was unable to open a service request from another application to which the operator had access. In this case, the Operator had access to the Canada and USA applications by default, but when a service request from the Canada application context was available in the list, the Get most urgent functionality failed to switch the application context from USA to Canada in order to open the work item. Investigation showed that the GetNextWork activity was being overridden in the Pega-DecisionManager ruleset in rule resolution and that the the Pega-ProcessEngine and Pega-DecisionManager had different versions of the activity. This has been resolved by upgrading GetNextWork in the Pega-DecisionManager ruleset.
SR-D7381 · Issue 486566
Purge/archive locking issue corrected
Resolved in Pega Version 8.1.6
Updates have been made to resolve a locking release issue for the pzBatchPurgeArchive activity.
SR-D23992 · Issue 494760
Null check added to handle portal refresh when first launched
Resolved in Pega Version 8.1.6
After configuring a button / dropdown in caseworker portal header with 'Refresh current action' onclick or onchange action, an exception appeared if the refresh harness was triggered and the Refresh did not happen. This was traced to the refresh harness happening after portal launch and before any DC action occurred. The portal 'history.state' is null at launch, meaning there was nothing to refresh. To handle this corner case, a null check has been added for the history state to avoid console errors.
SR-D11605 · Issue 485663
:JAWS correctly reads heading for Report browser/viewer
Resolved in Pega Version 8.1.6
JAWS 18 was not reading the titles in the report browser and report viewer as "heading level 1" as it should. For the Report Browser, JAWS was reading the title as "<title> - heading level 2", and for the Report Viewer, JAWS read the report title as "<title> - frame". This has been corrected by adding the appropriate aria tags to pzGetStyledLocalizedText.