SR-C1787 · Issue 346038
XSS filtering added for insHandle
Resolved in Pega Version 7.4
XSS filtering has been added for the inshandle parameter in the downloadFile activity.
SR-C1787 · Issue 320158
Exception message will not include invalid filename
Resolved in Pega Version 7.4
To enhance security, the exception message In the activity Rule-File-Binary.downloadFile will not display the invalid filename.
SR-B47858 · Issue 304348
Access Group Guardrail warning removed from password change
Resolved in Pega Version 7.4
Changing the password for the '[email protected]' operator generated the warning: 'The same Access Group should not be shared by Operators and Requestor Types. Access group PRPC:Agents was also referenced by Requestor Type DATA-ADMIN-REQUESTOR PRPC!BATCH'. The password change did take effect as expected. This guardrail warning was shown if the Access group used by the [email protected] operator, i.e. PRPC:Agents, was specified in any of Data-Admin-Requestor instance, and has been resolved by removing the unnecessary check.
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-B34028 · Issue 329193
Resolved error message on mandatory property in grid with Microsoft Internet Explorer
Resolved in Pega Version 7.4
When using Microsoft Internet Explorer, a property marked as mandatory inside a grid layout was firing its validation when the section was loaded. This caused an error icon to appear for a mandatory column on the first row when adding a new row from an always editable grid. This was traced to focus happening twice on the mandatory column, and has been fixed.
SR-B56628 · Issue 244337
Memory leaks fixed for CPM portal with Microsoft Internet Explorer
Resolved in Pega Version 7.4
Memory leaks were found in the CPM interaction portal that caused degraded performance, intermittent screen distortion, and browser screen freeze when using Microsoft Internet Explorer. To correct this, event listeners are now cleared at the end of every interaction so the memory allocated to them is released. In addition, a quickwrapup JS error has been resolved.
SR-B56628 · Issue 322412
Memory leaks fixed for CPM portal with Microsoft Internet Explorer
Resolved in Pega Version 7.4
Memory leaks were found in the CPM interaction portal that caused degraded performance, intermittent screen distortion, and browser screen freeze when using Microsoft Internet Explorer. To correct this, event listeners are now cleared at the end of every interaction so the memory allocated to them is released. In addition, a quickwrapup JS error has been resolved.
SR-B64560 · Issue 334877
Memory leaks fixed for CPM portal with Microsoft Internet Explorer
Resolved in Pega Version 7.4
Memory leaks were found in the CPM interaction portal that caused degraded performance, intermittent screen distortion, and browser screen freeze when using Microsoft Internet Explorer. To correct this, event listeners are now cleared at the end of every interaction so the memory allocated to them is released. In addition, a quickwrapup JS error has been resolved.