SR-127385 · Issue 235813
Fixed user authorization filtering error in extracts
Resolved in Pega Version 7.2.1
Extraction was failing sporadically due to the filter condition not being picked up by all the extract rules when running BIX. This was due to an error in authorizing the requestor with username/password causing differences in datetime formats, and has been fixed.
SR-A10345 · Issue 221893
Removed unexpected validation from Page-Change-Class
Resolved in Pega Version 7.2.1
Validation errors appeared on the review screen when tracer was enabled if there was non-conforming data in the non-expanded elements. PDN help for the activity method Page-Change-Class specifies that the method does not validate property values, but the generated java ends up calling DictionaryImpl.validate() and validates the step page without expanding it. Any invalid data in the non-expanded properties would be ignored. However, activating the tracer expands the page and as a result Page-Change-Class attempts to validate all the properties in the page, resulting in errors appearing when appropriate. In order to handle this scenario, validation has been removed from Page-Change-Class method in order to bring the results into line with the help documentation, and if validation is needed it must be added explicitly.
SR-A10491 · Issue 234174
Locking corrected for WebLogic BMT transactions
Resolved in Pega Version 7.2.1
Incomplete locking for WebLogic BMT transactions caused work items in the queue to be processed by duplicate agents even though the item was already processed. This has been fixed.
SR-A10653 · Issue 236942
Fixed NPE in the Connector and Metadata wizard
Resolved in Pega Version 7.2.1
The Connector and Metadata wizard was throwing a NPE in logs due to the inability to resolve a header schema definition during import. To fix this, the system will skip the unresolved header mapping processing and log an error message instead of creating an empty entry.
SR-A11437 · Issue 225251
Improve page sync and locking to avoid ConcurrentModifiedException
Resolved in Pega Version 7.2.1
There was a possibility that data page could be modified simultaneously and generate a ConcurrentModificationException, for example where a background thread is expanding a page to check messages at the same time a user thread is expanding the page to fire declaratives on read-only data page before marking it read only. This has been resolved by synchronizing access to a data page instance whenever there is an attempt to expand it from boundaries of data pages code.
SR-A11695 · Issue 229147
EXCEPTION_BLACKOUT time calculation fixed
Resolved in Pega Version 7.2.1
When calculating the time for the EXCEPTION_BLACKOUT period in EmailListener, the dimensions were incorrect due to errors in the sleep time observed when email listener failed to establish connection. This has been fixed.
SR-A12319 · Issue 226251
Repaired code generation for Single Page property reference
Resolved in Pega Version 7.2.1
Referencing a Single Page property in a Rule-Utility-Function parameter of type ClipboardPage generated Java that created a Clipboard Property at runtime, resulting in a ClassCastException. The code generation process for this was incorrect, and has been repaired.
SR-A12342 · Issue 226223
Standard System Usage Summary report updated with Daily Usage Table
Resolved in Pega Version 7.2.1
When the Standard System Usage Summary report was run, no users were shown even though users were able to access the system. The Hourly and Daily Usage Reports show data collection, but this was not propagated to the Summary report. This was an issue caused by the Summary Report not accepting values from the Daily Usage table, and schema updates have been made to fix this.
SR-A12464 · Issue 225916
Property Reference cache handing modified
Resolved in Pega Version 7.2.1
An issue with the property reference cache growing irrespective of the Cache Pruning threshold was traced to the omission of logic to handle references accessed via entry handles. This logic has been added. In addition, PropertyReferencePoolImpl has been modified with a new prconfig setting "cache/propertyreferencepool/enable" which defaults to true. This can be explicitly set to false to disable the pool.
SR-A12485 · Issue 227341
Improved validation error reporting for duplicate radio buttons
Resolved in Pega Version 7.2.1
The label of the radio buttons which contained a required field were not turning red when a validation error occurred if there were multiple radio buttons in the section configured with the same property name. Even though the other radio buttons were hidden by a visible 'when' condition, the label error was applied to the first instance of the radio button which contained the same name. To resolve this, the rule 'pega_validators.js' has been changed to check for duplicate radio buttons and identify the closest label to the field in the label.