SR-118283 · Issue 180166
Create New Work functionality smoothed for flows across multiple windows
Resolved in Pega Version 7.1.8
The Create New Work functionality in IAC was intermittently rendering incorrect data when opening a workflow in multiple windows. This was found to be a problem with PostDataId generated duplicate IDs for the different requests and has been changed to generate unique IDs.
SR-123051 · Issue 182680
LogOut' function corrected in the out-of-the-box operator menu
Resolved in Pega Version 7.1.8
When using the out-of-the-box provided "pyCaseMgrOperatorMenu" navigation rule, the menu contains two items - 'Preference's and 'LogOut'. Clicking on 'Log Out' was not performing log out operation. This was an error in the logout item of the navigation rule PYCASEMGROPERATORMENU, which was using an old script. This has been replaced with the new out-of-the-box logoff action.
SR-116908 · Issue 168347
When rules now display all text fields for function aliases
Resolved in Pega Version 7.1.7
Creating a new Access When rule failed to show the text fields for most available function aliases when a condition was added to the rule. This was an error in the passing of the classname to the function, and has been fixed.
SR-A3670 · Issue 207984
Added trim function for Operator full names exceeding max length
Resolved in Pega Version 7.1.9
If an OperatorID has a full name that exceeded 64 characters, the error ".pyWorkParty(Creator).pyLabel: "Ms [-------------------Operator Full Name--------------]" is too long, maximum length allowed is 64" appeared. To avoid this issue, the pyLabel will trim the full name to 63 characters.
SR-A9518 · Issue 220076
Rule-Utility-Function updated to handle name mismatch between versions
Resolved in Pega Version 7.2
After creating a MapTo library and function activity that was called via a File Service, the Simulation results returned an error that the function rule could not be found. This was caused by changes made to the TestFunction activity: in earlier versions with one String as a parameter it was named "TestFunction" and passed to the library APIs which invoked this function via reflection, but more recent versions generate the library name as "TestFunction--(String)". The name mismatch fails with a "no such method" exception. To support backward compatibility, updates have been made to getMapToUtlityMethod().
SR-A22365 · Issue 243530
Multi-parameter function value handling added to Report Definition chart
Resolved in Pega Version 7.2.1
When a chart control was configured using the property panel in design view, the chart preview did not update appropriately if it used a column defined by a function that with two or more parameters. To handle this, part of com.pega.pegarules.priv.desktop.reporting.chart.AutoChartConfigTranslator.translateDataItem(DataItem, ClipboardPage) has been refactored such that it only splits pyReportColumnKey on the first ',' (comma).
INC-139810 · Issue 592834
New Rule-Utility-Function added to allow customizing filename formatting in repository
Resolved in Pega Version 8.5.2
When using S3 as file storage, uploading a file with a name such as "sample.tar.gz" resulted in the file name in the repository being formatted as "sample.tar_.gz" instead of the expected "sample_.tar.gz". This was caused by the handling in pzSaveToRepository, which was meant to include the CaseID for the customer use case of same-name attachments on every instance of a case. In order to handle attachments with multiple file extensions such as "<FILE_NAME>.tar.gz", the logic for the fileName formatting has been moved from pzSaveToRepository to the new Rule-Utility-Function pyFormatAttachmentName so that is is possible to override and customize the behavior.
SR-C72252 · Issue 415223
isAncestorOf function now checks whether a child class is defined in the tenant layer
Resolved in Pega Version 8.2
After upgrade, the isAncestorOf function was not returning the correct result. Checking the inheritance path for the tenant work class showed the shared layer work class, but after upgrade of the tenant layer, the IsAncestorOf function returned false and the functionality that uses isAncestorOf function failed if the parent class was in the shared layer and the child was in the tenant layer. To correct this, the logic has been updated so that rather than always checking in the shared layer, the system will check whether the Descendant class is defined in the tenant first.
INC-139810 · Issue 592835
New Rule-Utility-Function added to allow customizing filename formatting in repository
Resolved in Pega Version 8.6
When using S3 as file storage, uploading a file with a name such as "sample.tar.gz" resulted in the file name in the repository being formatted as "sample.tar_.gz" instead of the expected "sample_.tar.gz". This was caused by the handling in pzSaveToRepository, which was meant to include the CaseID for the customer use case of same-name attachments on every instance of a case. In order to handle attachments with multiple file extensions such as "<FILE_NAME>.tar.gz", the logic for the fileName formatting has been moved from pzSaveToRepository to the new Rule-Utility-Function pyFormatAttachmentName so that is is possible to override and customize the behavior.
INC-167379 · Issue 640580
Unescape function added to CSR portal layout template rule
Resolved in Pega Version 8.5.4
When older sections previously used by the CSR portal were carried forward into more recent versions and were 'saved as' in the application ruleset, the error "Uncaught TypeError: pega.util.Dom.unescapeHTML is not a function" appeared. Dashboard loading took an excessive amount of time or didn't load at all, and no actions were working on the dashboard screen and tabs. This was traced to there being an older implementation of pega.util.Dom.unescapeHTML in pzpega_ui_template_layout_header, and this issue has been resolved by adding a custom unescape function in the rule itself so that it doesn't fail in cases where the dependent rule is not able to load the standard unescapeHTML utility.