SR-B15685 · Issue 317888
Mobile autocomplete dropdown selections fixed
Resolved in Pega Version 7.3.1
When the 'Enable lightweight autocomplete on phone' and 'Allow scrolling for more results' were enabled, the incorrect data was selected (e.g., using the autocomplete to select "John" from the list instead displayed "Mark"). This was due to a logic issue around the scroll feature for mobile list based autocomplete, and has been fixed.
SR-B71308 · Issue 319409
Paragraphs load as expected in offline app
Resolved in Pega Version 7.3.1
After upgrade, paragraph rules were not displaying as expected in the offline mobile app. Instead, the message 'Loading...' appeared in their place. This was traced to the records being returned correctly but not being properly packaged for display due to an error in the report definition. To correct this, a step has been added to the pzPackageLocalization activity to clear parameters which may mislead report execution.
SR-B71308 · Issue 320806
Paragraphs load as expected in offline app
Resolved in Pega Version 7.3.1
After upgrade, paragraph rules were not displaying as expected in the offline mobile app. Instead, the message 'Loading...' appeared in their place. This was traced to the records being returned correctly but not being properly packaged for display due to an error in the report definition. To correct this, a step has been added to the pzPackageLocalization activity to clear parameters which may mislead report execution.
SR-B65658 · Issue 314838
New case creation save errors resolved
Resolved in Pega Version 7.3.1
When a new case was created in an application built on top of Pega Pharmacovigilance, data propagation was throwing an error on the screen. Creation worked as expected when the pyDefault case type rule was opened and saved. This issue was traced to the case type rule not being created properly as part of the application creation, and has been resolved by updating pzDoesClassRequireBasicSave to not include Rule-Obj-CaseType in rows so the new application process performs a standard Save instead of an Obj-Save. In addition, it was not possible to save associated rules for selected data type when data type was in a locked ruleset and the pxUpdateRecord API was not setting pyrulename correctly when doing a save-as of the rule; these issues have also been corrected.
SR-B66453 · Issue 315656
New case creation save errors resolved
Resolved in Pega Version 7.3.1
When a new case was created in an application built on top of Pega Pharmacovigilance, data propagation was throwing an error on the screen. Creation worked as expected when the pyDefault case type rule was opened and saved. This issue was traced to the case type rule not being created properly as part of the application creation, and has been resolved by updating pzDoesClassRequireBasicSave to not include Rule-Obj-CaseType in rows so the new application process performs a standard Save instead of an Obj-Save. In addition, it was not possible to save associated rules for selected data type when data type was in a locked ruleset and the pxUpdateRecord API was not setting pyrulename correctly when doing a save-as of the rule; these issues have also been corrected.
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-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