SR-B52024 · Issue 308435
XSS filtering added to Chart Title
Resolved in Pega Version 7.3.1
XSS security filtering has been added to the Chart Title in the Chart Editor.
SR-B42729 · Issue 309850
Prgateway exception logging enhanced
Resolved in Pega Version 7.3.1
Stack trace logging has been enhanced for Prgateway exceptions.
SR-B42729 · Issue 309869
Prgateway exception logging enhanced
Resolved in Pega Version 7.3.1
Stack trace logging has been enhanced for Prgateway exceptions.
SR-B43915 · Issue 308088
Fixed Product Rule min and maxVersion value reset
Resolved in Pega Version 7.3.1
Values of mMinVersion and mMaxVersion were not being reset to null values after the "rulesets to include section" was processed in the product rule. This affected the "classes to include" section of the addSpecInstances() method as well, and happened only in special case when 'Rule-RuleSet-Version' class was included in the classes to include section. This resulted in the condition propagating from one section to another instead of clear initialization. This has been fixed by resetting the minVersion and maxVersion values after processing rulesets to include.
SR-B67118 · Issue 316911
Password obfuscated in serviceutils INFO message
Resolved in Pega Version 7.3.1
When running prpcServiceUtils.sh, the password from the property pega.rest.proxy.password was visible in an INFO statement due to the export with params listing all values including the password. The code has been revised so passwords will be obfuscated while logging in prpcServiceUtils.properties and not shown as plain text values.
SR-B56367 · Issue 313698
Query updated for Oracle DDL generation
Resolved in Pega Version 7.3.1
When using a class mapped to an external database view, creating a RAP that included a Data-Admin-DB-Table instance in a lower environment for import into a higher environment resulted in invalid generated DDL for the view. This was due to a column alias list in the view definition not being included in the generated DDL, and has been fixed by using a different metadata query for Oracle to ensure the column list is returned if it was originally specified.
SR-B67316 · Issue 317299
Query updated for Oracle DDL generation
Resolved in Pega Version 7.3.1
When using a class mapped to an external database view, creating a RAP that included a Data-Admin-DB-Table instance in a lower environment for import into a higher environment resulted in invalid generated DDL for the view. This was due to a column alias list in the view definition not being included in the generated DDL, and has been fixed by using a different metadata query for Oracle to ensure the column list is returned if it was originally specified.
SR-B44352 · Issue 306061
Fixed exported PDFs of scheduled email reports in DS
Resolved in Pega Version 7.3.1
Scheduled email reports that were converted to PDF were not readable, appearing as a list of rules in a very small font in white over a very light grey. This happened when the "export to pdf" command came from the designer studio; pzDesignerStudio was being picked and using a skin with new CSS features like font-size: inherit, color: inherit etc., which were not supported by the PD4ML library. As a workaround, it was possible to ignore the skin while exporting the PDF via enabling the "Ignore application skin when exporting to PDF" data access tab of the report, causing the system to consider the styles from the pyReport_ExportToPdfStyles available rule instead of skin. As a permanent fix, the system will avoid encountering parsing errors with PD4ML by loading "pyReport_ExportToPdfStyles" and automatically removing the skin file whenever export to PDF via designer studio is triggered.
SR-B48598 · Issue 305742
Fixed exported PDFs of scheduled email reports in DS
Resolved in Pega Version 7.3.1
Scheduled email reports that were converted to PDF were not readable, appearing as a list of rules in a very small font in white over a very light grey. This happened when the "export to pdf" command came from the designer studio; pzDesignerStudio was being picked and using a skin with new CSS features like font-size: inherit, color: inherit etc., which were not supported by the PD4ML library. As a workaround, it was possible to ignore the skin while exporting the PDF via enabling the "Ignore application skin when exporting to PDF" data access tab of the report, causing the system to consider the styles from the pyReport_ExportToPdfStyles available rule instead of skin. As a permanent fix, the system will avoid encountering parsing errors with PD4ML by loading "pyReport_ExportToPdfStyles" and automatically removing the skin file whenever export to PDF via designer studio is triggered.
SR-B50434 · Issue 317985
Struts mapping updated to compensate for behavior change
Resolved in Pega Version 7.3.1
The expectation was that after system startup in a zOS multi-servant environment where each servant has two JVMs which are running at any given point of time, launching SMA after adding a primary node should cause the servant node to show up in the edit page and upon submit the servant nodes should be listed under the primary node under left navigation links. However, after upgrade new nodes added to the cluster in the SMA were not visible due to behavior change between struts releases. This has been addressed by modifying the mapping in struts.xml and tuning some JSP syntax issues in AddNodeIDs.jsp.