SR-C90467 · Issue 429608
Validations are correctly run on rescheduled reports
Resolved in Pega Version 8.2.2
When using the OOTB schedule report functionality, UI validations were bypassed if the existing schedule was deleted and the report was rescheduled. This has been corrected by updating the Review harness to display the Perform harness when clicking Update.
SR-D30944 · Issue 503232
Corrected pagination alignment in tabbed layout sourced from RD
Resolved in Pega Version 8.2.4
Pagination numbers were not being presented inline with the next/back arrows when using a tabbed table layout with source:report definition. To resolve this, the pyGridPaginator function has been added to Pega-Gadgets in Work- .
SR-D30944 · Issue 503231
Corrected pagination alignment in tabbed layout sourced from RD
Resolved in Pega Version 8.3.1
Pagination numbers were not being presented inline with the next/back arrows when using a tabbed table layout with source:report definition. To resolve this, the pyGridPaginator function has been added to Pega-Gadgets in Work- .
SR-D86079 · Issue 548108
Label truncation added for pinned item title
Resolved in Pega Version 8.3.3
While pinning a Space, document, or URL, the length of the item title was causing validation issues if it exceeded 64 characters. This has been resolved by modifying the pzGetPins activity to truncate pyLabel to 64 characters using the truncateLongText function.
SR-116209 · Issue 166698
Backslash '\' now showing as expected in autocomplete and search
Resolved in Pega Version 7.1.7
The AutoComplete control was filtering out backslash '\' characters when displaying the values in the list of matches, causing failures with search and autocomplete. The Rule-Utility-Function for the getProperty has been corrected to allow '\' to be handled properly.
SR-133163 · Issue 203273
Refined property-set expansion to support complex activities
Resolved in Pega Version 7.2
Attempting to expand a property-set in an activity with many steps (20+) caused a failure and the activity locked up. Tin order to support complex activities, the activity call and clipboard functions in this call have been refined for efficiency.
INC-193047 · Issue 694049
Added handling for nested clipboard pages
Resolved in Pega Version 8.6.3
On save of sections that have items (cells) nested more than one layer deep and have either "Show menu" or "Run data transform" actions, silent errors were found in the tracer indicating "Attempting to access a rule with a bad defined-on class: Trying to open rule ... of class "Rule-Navigation", but no defined-on class (pyClassName) was specified". This was due to the pzActionShowMenu Rule-Utility-Function and pzActionRunDataTransform Rule-Utility-Function assuming the clipboard page structure was only one layer deep, and has been resolved by using findRulePageFromCurrentPage from SectionUtils.java .
INC-193047 · Issue 697578
Added handling for nested clipboard pages
Resolved in Pega Version 8.7.1
On save of sections that have items (cells) nested more than one layer deep and have either "Show menu" or "Run data transform" actions, silent errors were found in the tracer indicating "Attempting to access a rule with a bad defined-on class: Trying to open rule ... of class "Rule-Navigation", but no defined-on class (pyClassName) was specified". This was due to the pzActionShowMenu Rule-Utility-Function and pzActionRunDataTransform Rule-Utility-Function assuming the clipboard page structure was only one layer deep, and has been resolved by using findRulePageFromCurrentPage from SectionUtils.java
SR-B86387 · Issue 339475
Offline mobile Work ID sync issue fixed
Resolved in Pega Version 7.4
When creating a new Case on the mobile offline application, temporary IDs are created. Once synced with the server, the Server IDs are correctly updated on the device. However, if 3-4 new cases were created, one case was failing due to the Server ID not correctly being updated on the device. This meant the device still carried the temp ID and failed to sync. This was traced to EventListener_executeFunction returning false when there was any exception in the subscribed function during its execution, making the subscriber function null in the Listeners array. To fix this, a safe check has been added in syncAttachmentDP and a try catch has been added in dataPageUpdateAction to handle the exceptions.
INC-131151 · Issue 572832
Resolved empty body for Reject email
Resolved in Pega Version 8.1.9
When using the pzEmailActions Section in Correspondence for Approve/ Reject functionality via email, there was no reply body in the email for Reject Option. This was due to the flow action for the Reject email being different than that of the Approve email, and has been resolved.