SR-B5813 · Issue 276080
DuplicateProperty checked on enqueue
Resolved in Pega Version 7.3
The enqueue() method of PRQueueManager was not honoring the "pyDuplicateProperty" value of the existing queue items which have a higher pyMinimumDateTimeForProcessing. To correct this, QueueManagerImpl has been modified so the enqueue() method uses an overloaded version of next() method which is intended to ignore pyMinimumAgeForProcessing when checking for duplicates.
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-B5982 · Issue 279431
Tabbed form submission errors read by JAWS
Resolved in Pega Version 7.3
JAWS was not reading the error messages on the screen if the form submission was in a tabbed layout. To correct this, a setTimeout has been added to the reloadAcessibility function to call displayErrorTable.
SR-B613 · Issue 273665
Null check added to RecalculateAndSave
Resolved in Pega Version 7.3
A null-pointer exception occurred during an index operation within the deferred save in RecalculateAndSave due to the context page being null during declare index processing. A null check has been added for the context page to resolve this.
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-B6161 · Issue 275612
RD generating checkbox control as T/F image fixed
Resolved in Pega Version 7.3
A report definition was not showing checkbox controls as images for true/false properties when generated automatically. This has been fixed.
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 277566
BIX extraction config documentation updated
Resolved in Pega Version 7.3
When using command-line BIX 7.1 to extract records and write them to a secondary database, it appeared that some of the records got skipped. This was actually expected behavior: 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 eliminate this confusion, the log message has been clarified. In addition, the information in the Guide indicated that if bix/useHistoryClasses was set to true, the generated query should always use the history table and not the actual work object table. However, it was not made clear that the BIX code does not use this option for explicit command line arguments. Therefore, the following text has been added to the BIX documentation under "Configuring the extraction environment" -> "Configuring optional prconfig.xml settings": Including class instances added during a batch run To ensure that class instances added to the Pega Platform database after a batch run begins execution are included in the extract, add the following property:
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-B6244 · Issue 277566
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.