SR-A16406 · Issue 231876
Validation handling added for complex criteria values
Resolved in Pega Version 7.2.1
Incorrect validations were appearing when trying to save a List View rule with a criteria value that uses a property embedded in the pxResults page of a declare page in the Value field of the Content tab and that listed the top level declare page in Pages & Classes. This was due to the unusual structure of this referred property not automatically having the necessary links to retrieve the necessary pages and classes, and handling has been added for this special scenario.
SR-A16432 · Issue 232172
Repaired Parse-Byte-Pos in File Listener
Resolved in Pega Version 7.2.1
Due to missing encoding for the type, files in byte format caused a NPE in file listener. This has been fixed.
SR-A16449 · Issue 234627
Java Mail API updated
Resolved in Pega Version 7.2.1
A bug in the Java Mail API 1.5.2 jar caused intermittent failures in receiving email. The API has been updated to the 1.5.3 jar.
SR-A16535 · Issue 231740
Null Boolean and datetime properties passed in command line extraction
Resolved in Pega Version 7.2.1
If a Boolean or a datetime Embedded valuelist /valuegroup /pagelist/page group property was in the WO blob but has no value when extracted from the command line using the -B and -J options, the value in the extract was not valid. This was traced to the handling for empty Boolean and datetime properties, and these properties will now be passed without modification when using the command line options -B and -J in XML output format or when running the extract from the UI.
SR-A16543 · Issue 235300
Resolved Interaction Portal unexpected close
Resolved in Pega Version 7.2.1
In Google Chrome, launching a secondary portal and encountering a Content Security Policy issue relating to an image caused the secondary portal to automatically close and the developer portal to be refreshed. This was an issue with a mismatch in the pyrequestor token, and has been corrected.
SR-A16566 · Issue 232088
TrackAction and TrackAchievement no longer require authentication to run
Resolved in Pega Version 7.2.1
When an unauthenticated client called an external service (Service-HTTP, SOAP, etc.) that upon completion uses an activity that uses Requestor-Stop instead of allowing the requestor to time out, an error was generated. This was due to the new rule PXTRACKACTION defaulting to 'Require authentication to run', a conflict when an unauthenticated service invokes this activity. The 'Require authentication to run' setting has been unchecked for the pxTrackAction and pxTrackAchievement activities.
SR-A16582 · Issue 233320
Improved BIX extract handling for multiple active agents
Resolved in Pega Version 7.2.1
When multiple agents were scheduled to run extracts at the same time by utilizing pxExtractDataWithArgs, there was intermittent failure in creating the manifest files. The BIX log would not contain an entry for the files being created, no error was displayed, and agents sometimes needed to be restarted. This was an issue with incomplete extraction of the output data and manifest files due to the PAL timer overriding the current thread context as it handled each of the multiple calls. To resolve this, the previous static variables used to store thread and requester instances have been made private to ensure reliability when handling parallel extracts and simultaneous runs.
SR-A16598 · Issue 233879
Work party change refreshes existing harness
Resolved in Pega Version 7.2.1
If a work party was added to a case and the page was then refreshed at the browser level by hitting F5, a new harness appeared for the case type instead of the existing harness. The action order in the on-change action has been updated to correct this.
SR-A16621 · Issue 233386
Changed image tag to prevent auto-submit of calendar when parameters exceeded
Resolved in Pega Version 7.2.1
When user wanted to select the future date, he navigates by clicking the Year navigation link (arrow link). During this process of selecting a future date in the Year Navigation link, moving beyond the configured Number of years caused the page to be automatically submitted. This was caused by the input tag used for image causing a form submit, and tag has been changed to an anchor to fix this.
SR-A16638 · Issue 233607
Changed edit control to prevent Google Chrome adding zeroes when localizing
Resolved in Pega Version 7.2.1
When using Google Chrome in some locales, zeros were being added to values in the skin and corrupting entered values. This was due to Google Chrome defaulting to localizing input type numbers, which caused dual localization after the control had already localized the value after reload. When input type is text, only the control localization will happen, so a workaround for Google Chrome has been added where the type of control has bene changed to text in the editable mode for the pyItemAlignment section.