SR-D33930 · Issue 507970
Check added to pyWorkPage before context page replacement
Resolved in Pega Version 8.3.1
When given an assignment configured with Save and Next buttons where the on-click of the Next button triggered FinishAssignment and the case type used Optimistic locking, the workobject lock was not acquired and an error was thrown when clicking Save and then the Next button. Investigation showed that the lock was not acquired because the pyCaseUpdateInfo page was not available in the work object under pyWorkPage. This was traced to the 'When' condition used to display the delete icon on a pulse post. This When condition needs to be evaluated on the context page (in this case, the work page), but when multiple posts are present on the WorkObject) the pyWorkPage was being replaced with a fresh copy from the DB and any updates on the current work page were lost. To resolve this, the behavior has been changed from always creating a context page to only creating the context page if one does not already exist on the Thread.
SR-D7323 · Issue 493176
Pin Case to Board updated to use unique IDs for different workpools
Resolved in Pega Version 8.3.1
When using the Pin Case to Board functionality, it was only possible to find and pin cases in the default/current work pool of the working access group and not any other cases in any other work pools which allowed access to open/search/process. This was due to pyLabel being used to compare if a value entered was valid, which was not a unique key. To resolve this, the pyValidatePinDetails activity in Pega-Ext-Mentions-Documents, Pega-Ext-Mentions-Cases, and Pega-Ext-Mentions-Groups classes have been updated to compare pzInsKey instead of pyLabel to check for validate pin.
SR-D18853 · Issue 488283
Visibility on client check removed to enable Pulse on click
Resolved in Pega Version 8.3.1
When Pulse was configured on click of a icon, the comment section was not visible. Investigation showed that at the time of DOM load, pyMessage property was not available in the DOM because 'Run visibility condition on client' was checked by default. Visibility on client checks have been removed to resolve this issue.
SR-D37757 · Issue 507966
Pulse delete icon repaired
Resolved in Pega Version 8.3.1
After upgrade, it was no longer possible to delete one's own comment in Pulse. This was traced to the section pzDeleteMessage having two dynamic layouts with icon as image configured. During runtime, this section was present in the DOM yet the icons were not visible when the conditions configured were returned as true. This was caused by an error in the generated java for the layout, and has been corrected.
SR-D44012 · Issue 509880
Added more error handling in pzCreateThumbnail
Resolved in Pega Version 8.3.1
In activity pzCreateThumbnail, a null pointer error was generated at step 2. This was traced to the value of originalImage being null even though there was no error in the image file itself, and has been resolved by adding an error check .
SR-D18814 · Issue 493323
Enhancement added to fetch HTML attachment from CMS
Resolved in Pega Version 8.3.1
When email containing HTML was sent to the Listener, some of the characters were not getting decoded properly when viewing. In this case, HTML email content was saved as an attachment in CMS , and this error was traced to the system being unable to fetch the attachment. To resolve this, an enhancement has been added to fetch non-Pega DB attachments using pxGetFileAttachmentContent.
SR-D23360 · Issue 493463
Email reply with same attachment name correctly processed
Resolved in Pega Version 8.3.1
When an email reply was received with an attachment using the same name as one received earlier, the new attachment was not getting processed and the message 'The Specified file/folder already exists in the target repository. Please specify a different file/folder' appeared. This was traced to an incomplete check for the object class that did not qualify the attachment name for a reply, and as been corrected.
SR-D29832 · Issue 503224
Corrected image alignment for email case creation
Resolved in Pega Version 8.3.1
An issue with missing image styling when an email was sent to create a case was traced to the Owasp library stripping align attributes from the img tag. This has been fixed.
SR-D18879 · Issue 500640
Logic update made to PrepareColors to resolve calculation ambiguity
Resolved in Pega Version 8.3.1
When a Report Definition was summarized, the executed report showed a graph for multiple categories but generated the error "No data to display" if given a single category. This was traced to an ambiguity in the Java syntax of the Rule-Utility-Function pzPrepareColors that led to a NegativeArraySizeException on a customer's environment. To resolve this, parentheses have been placed around a ternary operator to ensure the correct order of operations.
SR-D21527 · Issue 491736
Hidden filters will not be shown on the resulting report
Resolved in Pega Version 8.3.1
After setting up a Report Definition to be visible in report browser with all filters hidden, editing and saving the report resulted in the filter values being visible on the report. This has been resolved by modifying pzResolveCopyFilters activity so that If the filter view option is "Read only, allow no changes" and "Filter not visible in Viewer", it will skip copying the filter values on to the report definition page.