SR-B66932 · Issue 334833
Indexes created on a MT system automatically contain pzTenantID column
Resolved in Pega Version 7.4
When installing PDC on a multi-tenant system the pzTenantID column is automatically added to every application table (pegaam_*). This is expected. However, the indexes contained in the schema jar were not automatically extended to contain the pzTenantID, which created the need to manually update all indexes post-install to include the pzTenantID column on the first place. A similar problem existed when updating to a newer version of PDC that contains schema changes. This has been addressed by adding MultiTenantPolicy and Import/Default concrete classes that inform DatabaseSchemaGenerator.IndexElement whether or not to include pzTenantID in the column list. During Import, pzTenantID will be added to all indexes on shared context tables. In other utilities (UAS, clone table, etc.) the column will only be added to primary key and unique indexes/constraints (existing behavior).
SR-B83849 · Issue 337067
Exception handling added for XML with invalid characters
Resolved in Pega Version 7.4
When PDC receives an Exception alert in the form of a SOAP Message from one of its monitored nodes, it parses the XML and creates a work object from it. However, if the Exception was caused by an XML with invalid characters, the Exception SOAP Alert message carried the invalid characters when arriving on AES/PDC PRSOAPServlet, causing the engine to fail in parsing the XML and generate an exception. Logic has now been added to SOAP envelope parsing to catch the exception, sanitize the payload, and then re-feed it to the parser.
SR-C445 · Issue 344716
cluster rule watch lock expires on crash
Resolved in Pega Version 7.4
If the cluster rule watch was in progress and the browser / system crashed, the rule watch became locked until the system (cluster) was restarted. In this case, the disconnect command from Req1 has an encrypted requestor ID because it is an unauthenticated requestor, leading to all String-matches failing. A hook to delete all entries in the distributed rule watch map for a given requestor during its clean up has now been added to resolve this.
SR-B90037 · Issue 340248
pyFolderID honored for SaveFileContent
Resolved in Pega Version 7.4
After customizing the out-of-the-box Activity "SaveFileContent" by setting the property "pyFolderID," all attachments were stored in the Documentum root folder instead of the specified folder. This was traced to a code error that bypassed setting the parameter, and has been fixed.
SR-D40662 · Issue 511397
OpenRuleAdvanced updated
Resolved in Pega Version 8.2.5
After upgrade, the Update Page and Append and Map to step in Data transform was generating the error "No Server connection while giving page name to Target and Source". This was traced to the OpenRuleAdvanced_OverLabel control, and investigation showed that a variable was not being resolved when invoking pzEncryptURLActionString. This has been resolved by updating OpenRuleAdvanced and reimplementing two parameters as well as moving the call of these variables to the beginning of the script. Security has also been improved by moving some of the encryption to SafeUrls.
SR-D42566 · Issue 512872
Security improvements for ApplicationInventory and Delete Class
Resolved in Pega Version 8.2.5
It was possible to call the activity "ApplicationInventory of class Rule-" by appending the activity name in the URL. To improve security, the ApplicationInventory activity and HTML rule have been removed from the system. In addition, it was possible to access the "delete class" screen and perform actions on top of it by directly appending the stream to the URL. This has been refactored so the screen will be presented only if the pzSystemOperationsAdministrator privilege is in the current access group.
SR-D43402 · Issue 509972
ValueList/Group correctly appears on clipboard
Resolved in Pega Version 8.2.5
After upgrade the property of type ValueList/Group was missing from the clipboard. This was traced to an extra 'when' rule applied on the visibility of Layout-2 in final section pzProperty (Pega-Desktop:08-02-01), and has been corrected.
SR-D43776 · Issue 510762
Clipboard ExecuteActivity button updated to get classname
Resolved in Pega Version 8.2.5
In Clipboard, clicking the execute activity button did not trigger any action in the backend. Investigation showed that previously the ID attribute for the HTML element used to be same as the property name, and the value of property "pyClassName" was found in the document.getElementById function. Due to work done to provide a feature that generates unique IDs for UI elements (auto generated controls), this must be done through other functions such as document.querySelector to get the value of the property from DOM. The necessary updates have now been made to the javascript function in control pzExecuteActivityButton.
SR-D43783 · Issue 509908
Comments explicitly excluded from generated ruleset under localization
Resolved in Pega Version 8.2.5
A generated URL link from Correspondence Fragment (WorkLink) which was saved in Pega-ProCom_ja was incorrect due to an incomplete URL. The ruleset Pega-ProCom_ja is not provided from the platform, but is generated when using localization. In this case, a comment fragment was included in the rule when it was generated, causing the issue. To resolve this, comment handling has been updated to ensure it's not included when generating the rule.
SR-D49792 · Issue 515982
Corrected property mismatch in Create Eligibility condition builder
Resolved in Pega Version 8.2.5
A parameter mismatch in Create Eligibility condition builder was resulting in properties not being offered in the dropdowns as expected when the top level page was not CaseTypeStages or this page did not exist on clipboard. This has been resolved by changing CaseTypeStages.pyClassName to ConditionsParamterPage.pyClassName in the pzSelectValues_FieldType section.