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-B48904 · Issue 309328
Localization added to Pega Marketing components
Resolved in Pega Version 7.3.1
Localization support for German, Japanese, Spanish, Italian, French and Chinese simplified has been added for the Pega Marketing application for these components: Proposition Management Landing pages - Issue, Group creation, Un Versioned and Versioned Proposition Creation, Conversion from UnVersioned to Versioned proposition, Decision Data Form, Interaction History Data Set & IH Landing Page, VBD & KPI navigation links from Designer Studio and its Landing Pages. Note : out-of-the-box properties/property values, controls, and pop-ups, can not be localized in these functionalities.
SR-B48904 · Issue 315159
Localization added to Pega Marketing components
Resolved in Pega Version 7.3.1
Localization support for German, Japanese, Spanish, Italian, French and Chinese simplified has been added for the Pega Marketing application for these components: Proposition Management Landing pages - Issue, Group creation, Un Versioned and Versioned Proposition Creation, Conversion from UnVersioned to Versioned proposition, Decision Data Form, Interaction History Data Set & IH Landing Page, VBD & KPI navigation links from Designer Studio and its Landing Pages. Note : out-of-the-box properties/property values, controls, and pop-ups, can not be localized in these functionalities.
SR-B50202 · Issue 308172
Pre- and Post-processing modified to support customized circumstanced FA
Resolved in Pega Version 7.3.1
A customized out-of-the-box Flow Action called "CheckIn" was created by modifying a circumstanced version with property .pxObjClass = Rule-Admin-Product. For any Product rule, attempting checkin called this customized Flow Action as expected. However, the pre-processing activity and post-processing activity added in the circumstanced Flow Action "CheckIn" were not invoked at all; instead, the pre-processing activity and post-processing activity in the base Flow Action "CheckIn" were triggered. This was due to circumstancing not working when used with the doAction() method because it does not reset the primary page when it invokes a rule. It passes a step page for use by the rule. In order to support this customization, the function will call to tools.doActivity() with the same arguments instead of doAction(), which will force the engine to push myWorkPage as the new primary page for the duration of the call (and then pop it after the call completes). This should provide the correct context for the circumstancing to call the circumstanced purpose code.
SR-B51844 · Issue 312363
Carriage return characters escaped in automated JSON data
Resolved in Pega Version 7.3.1
Automated JSON data received from the system containing carriage return characters such as \n, \r, \t caused parsing issues. To resolve this, changes have been made in the webwb-pzPega_ui_roboticAutomation-js file such that all carriage return characters such as \n,\r,\t will be handled using an escape sequence.
SR-B54666 · Issue 320294
Paragraphs load as expected in offline app
Resolved in Pega Version 7.3.1
A paragraph rule that included a jsp reference tag for an integer type property did not display properly when tested in an offline mobile app, instead hanging at the "Loading..." message indicator. This was due to getLocalizedTextForString() failing for non-string values, and has been fixed with a check in template_paragraph.js
SR-B54666 · Issue 316346
Paragraphs load as expected in offline app
Resolved in Pega Version 7.3.1
A paragraph rule that included a jsp reference tag for an integer type property did not display properly when tested in an offline mobile app, instead hanging at the "Loading..." message indicator. This was due to getLocalizedTextForString() failing for non-string values, and has been fixed with a check in template_paragraph.js
SR-B63171 · Issue 315061
Pre- and Post-processing modified to support customized circumstanced FA
Resolved in Pega Version 7.3.1
A customized out-of-the-box Flow Action called "CheckIn" was created by modifying a circumstanced version with property .pxObjClass = Rule-Admin-Product. For any Product rule, attempting checkin called this customized Flow Action as expected. However, the pre-processing activity and post-processing activity added in the circumstanced Flow Action "CheckIn" were not invoked at all; instead, the pre-processing activity and post-processing activity in the base Flow Action "CheckIn" were triggered. This was due to circumstancing not working when used with the doAction() method because it does not reset the primary page when it invokes a rule. It passes a step page for use by the rule. In order to support this customization, the function will call to tools.doActivity() with the same arguments instead of doAction(), which will force the engine to push myWorkPage as the new primary page for the duration of the call (and then pop it after the call completes). This should provide the correct context for the circumstancing to call the circumstanced purpose code.
SR-B65755 · Issue 314416
Broken-Process SLA update API changed
Resolved in Pega Version 7.3.1
When an SLA update on a work object occurred and the current SLA was in Broken-Process Status, the action failed with the error "The Flow Action post-processing activity ActionChangeAssignmentSLAProps failed: Instance of class Queue not found". This was an issue where dequeuing the SLA entry item to update it with new time caused a status conflict with the blob. To avoid this, the activity ActionChangeAssignmentSLAProps has been updated to use the API updateDeferred(page,repairBroken) which accepts a Boolean if it has to repair a broken item. Setting the repairBroken flag to 'true' will bypass the call to dequeue.