SR-A4279 · Issue 210830
Added handling for unknown UpdateDateType property
Resolved in Pega Version 7.1.9
Saving a Flow stream triggers the pzTrackChangesForFlow activity call, which then reads the pxUpdateDateTime property and converts it to Big Decimal for comparison. This conversion requires mode of the property (i.e. DateTime (?M?) in this case) to be known, which is specified in blob as encoded format. When using a PCI framework where the mode of the pxUpdateDateTime property is unknown(???), a NumberFormatException was generated. This has been fixed.
SR-A469 · Issue 210020
Reworked config file search to prevent WebSphere looping
Resolved in Pega Version 7.1.9
During server startup, the engine tries to populate the environment properties by reading the config files for the application server. A problem was found in some installations with WebSphere where trying to locate the XML file containing the information on the server port created an infinite loop that caused the engine startup to hang. To resolve this, the search function call now has been replaced by another method that tries to obtain the same information from config service without having to locate the XML file.
SR-A903 · Issue 204609
Removed primary page requirement for link-object activity
Resolved in Pega Version 7.1.9
When using the link-object activity method with the history checkmark and the specified step page without providing a primary page, the link-object activity method caused a null-pointer-exception when it attempted to fetch data from the pxRequestor page. This was caused by an unnecessary reference to the primary page, and the method to retrieve the value of pyUserIdentifier has been updated.
SR-A92 · Issue 203202
Removed extra slash character being appended in prconfig
Resolved in Pega Version 7.1.9
When configuring prconfig settings, an extra slash was getting appended when the sethtmlbasecontext had trailing slash in the URL. This has been corrected.
SR-A955 · Issue 204118
Fixed typo in error message
Resolved in Pega Version 7.1.9
A typo in an HA status message written to the log has been corrected.
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-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-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-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.