SR-B5417 · Issue 274794
Logic added to convert UTC Date for REST clipboard mapping
Resolved in Pega Version 7.3
An error was generated while mapping UTC format Date fields to the clipboard in REST. This was traced to the DateTime properties in the JSON response not being converted to Pega-supported datetime format, and the necessary parsing logic has been added.
SR-B5820 · Issue 276037
Properties of type Integer text value properly formatted
Resolved in Pega Version 7.3
Properties of type Integer text value were not properly formatted when set to property. This has been fixed by modifying the assembler code to pass the property type and use it properly for runtime mapping.
SR-B6158 · Issue 275668
Updated mobile attachment error handling
Resolved in Pega Version 7.3
Incorrect behavior was seen on mobile when limiting file types using a trigger / when rule. The file type was ultimately evaluated and not attached, but the 'File attached Successfully' message was displayed on the mobile device. This has been fixed with an added check to evaluate whether the attachment is one of the accepted types, and the error markup has been updated.
SR-B6165 · Issue 278927
Trend Reporting list view error resolved
Resolved in Pega Version 7.3
After running a Summary View with Trend Reporting, the following error appeared in the logs: NumberFormatException For input string: " ". This was caused by the data transform for the trend reporting list view initializing a null value for pyCeilingField as " " instead of "", and has been fixed.
SR-B6244 · Issue 277565
Documentation and log messages updated for BIX/useHistoryClasses
Resolved in Pega Version 7.3
When using command-line BIX 7.1 to extract records and write them to a secondary database, messages from the system gave the impression that some of the records were skipped. This was due to a mismatch in the number of records reported at different points in the extraction: as the records got updated while the extract was running, those particular updated records got skipped as they did not fall into the time range that user was passing. To avoid this confusion, the text in the logs has been clarified to read: "Processing Class class name with XXXX instances (processing count may vary as records get modified before BIX extraction)." In addition, the documentation regarding the usage of the BIX/useHistoryClasses option has been updated to reflect this information.
SR-B6500 · Issue 276002
Mobile performance improvements for static content load
Resolved in Pega Version 7.3
Performance improvements have been made for mobile by enabling concurrent parallel load of static content.
SR-B6704 · Issue 289314
Auto-populate updated for better page copy references
Resolved in Pega Version 7.3
After upgrade, an error was generated at a page-remove step on the Group information screen while running the quoting process. This happened in cases where a copy was made of a page containing an auto populate property and the data page referred by the AP had Common Parent references, and was traced to the parent page of the reference property having been removed from the common parent page. To resolve this, the auto-populate function has been updated to better maintain references in copies.
SR-B6971 · Issue 285310
Error propagation corrected for RDB-Save with RunInParallel
Resolved in Pega Version 7.3
If several Connect SQLs were called via the RDB-Save activity method with RunInParallel selected, failure of one of the Connect SQLs was not being caught and no errors were captured. This was traced to a situation where an exception thrown at the childcase with this combination of settings was propagated to the parent, and has been corrected by adding a Data-Admin-System-Setting "isPropagateExceptionFromChildToParent" defined in "Pega-RULES" ruleset, which has a default value of "true" only for RDB-Save method (not for all RDB-methods).
SR-B6971 · Issue 279537
Error propagation corrected for RDB-Save with RunInParallel
Resolved in Pega Version 7.3
If several Connect SQLs were called via the RDB-Save activity method with RunInParallel selected, failure of one of the Connect SQLs was not being caught and no errors were captured. This was traced to a situation where an exception thrown at the childcase with this combination of settings was propagated to the parent, and has been corrected by adding a Data-Admin-System-Setting "isPropagateExceptionFromChildToParent" defined in "Pega-RULES" ruleset, which has a default value of "true" only for RDB-Save method (not for all RDB-methods).
SR-B6980 · Issue 278169
fixed naming in multiple extracts run from the command line
Resolved in Pega Version 7.3
When running multiple comma separated extracts at a time using command lineoption -i, all of the rules in the manifest file contained the value of the last extract name only. This was a missed use case, and ExtractImpl has been modified to correct it.