SR-D51535 · Issue 519476
Enhanced discrimination for tasks in MyPega spaces
Resolved in Pega Version 8.4
When using My Pega for spaces and tasks, using drag and drop to move many cases around quickly resulted in tasks intermittently ending up in a state where they could not be updated further and became unusable. Analysis showed that because the milliseconds part of the update time was rounded, the logic of comparing for value between 0 and 1000 failed when the comparison returned -ve value. To resolve this, the comparison has been modified to !=0 and the 'when' rule pyContinueTaskProcessing has been added as an extension along with the appropriate usage guide to restrict processing. By default, the system will consider task name, description, due date, assignee, and rank properties; if more properties are needed to evaluate, this when rule can help.
SR-D54200 · Issue 516776
Custom attachment category parameter passed to dropdown
Resolved in Pega Version 8.4
Attempting to use the out-of-the-box “Attachments control” which was configured at design time to use a custom category where both the custom category and the section class were in the same work class resulted in the attachment category dropdown defaulting to “File” instead of the custom category. Investigation showed that the custom attachment category name configured on the control was missing in one of the pre-processing activities sequence. To resolve this, the activity Work-.pzInitAttachContent and the initAttachmentPage activity have been updated to pass the custom attachment category parameter.
SR-D67323 · Issue 529948
XSS filtering added for CreateMergedWordDoc
Resolved in Pega Version 8.4
XSS filtering has been added for the TemplateName parameter value in the CreateMergedWordDoc section.
SR-D33227 · Issue 510826
Check added for lock expiration when using Save for Default locking
Resolved in Pega Version 8.4
With the default case locking policy, during the process from creating a Case Object to Submit it was possible for multiple users to edit and save the same work object if the lock expired for the original user. No warnings appeared. To resolve this, handling has been added for a lock expiration scenario: previously, Save for Default locking was not considered. This has now been updated with a check that will evaluate whether or not the lock is gone before attempting to save.
SR-D22415 · Issue 493439
Enhancement added to expose BrowserAttachmentTypeTable
Resolved in Pega Version 8.3.1
By default, the inline view of PDF files appears with the thread name visible. An enhancement has been made to expose pzBrowserAttachmentTypeTable as a py rule: when the DT is overridden such that return is false for PDF, the inline view is not displayed but instead the PDF is downloaded when clicked.
SR-D23723 · Issue 503087
pxGenerateExcelFile updated for handling blank dates
Resolved in Pega Version 8.3.1
When using a custom template for exporting to Excel, blank DateTime property column values defaulted to the current date. To resolve this, the pxGenerateExcelFile activity has been updated to ensure that an empty date will be exported as blank and that given dates will appear in the correct datetime format.
SR-D26589 · Issue 496719
pxParseExcelFile activity will now parse multiple sheets
Resolved in Pega Version 8.3.1
When trying to use the activity pxParseExcelFile on an Excel file containing three sheets where each sheet had a different pagelist, the properties mentioned in sheet 1 were populated on upload but the remaining sheets only showed the error message "Could not get clipboard property for reference Work Queues.". This was caused by an error in Row index handling for the additional sheets, and has been resolved by updating the logic to populate the data in the clipboard. Additional issues for this issue in 8.4 to fix issues like formulae not getting evaluated and $ not parsed: 501592, 501383
SR-D29114 · Issue 499930
Added handling for bulleted text insert triggering audit
Resolved in Pega Version 8.3.1
When a bulleted text (copied from an email or rich text ) was used in the text area property, the audit considered it as a change even when there was no change. This was tracked to the field value 'pyHistoryMemo • ChangeTrack_Add' in @baseclass which is being used to get the localized value for audit memo: the field value accepts only 2 parameters, but the inserted text area input contained the '\t' that is used for parameter translation. To resolve this, the system will call the addMemoForSecurityChangeTracking utility method to replace all \t's present in both the Current Value and Previous value with 'empty' such that no '\t' characters are available in either of the string parameters.
SR-D37444 · Issue 507037
WorkBasketGadget control updated for improved backwards compatibility
Resolved in Pega Version 8.3.1
After upgrade, the WorkBasketGadget Control was not retrieving the work queues. This was traced to a backwards compatibility issue introduced when greater security was put in place. The control WorkBasketGadget contains a call to pzEncryptURLActionString that was introduced in 8.x versions of the platform to encrypt URLs to avoid hijacking. The content of the URL relies on the pxRequestor.pxWorkGroup property, which is resolved using pega:reference tags. This approach was working in versions below 8.x, but these tags were not resolved at runtime. To correct this, requestorWorkGroup will be resolved as string and passed as a parameter instead of using pega:reference tags.
SR-D50144 · Issue 513684
Dynamic RTE support added to Word document generation
Resolved in Pega Version 8.3.1
Pega document generation from a Word template was not properly replacing field codes in the document header or footer and failed to render images embedded in rich text fields. An enhancement has now been added to pzGenerateDocument which will support dynamic content from RTE.