SR-A43745 · Issue 249270
Copied ticket shapes properly visible on Work Management
Resolved in Pega Version 7.2.2
After correcting a problem with the XML generated by ticket shapes related to work states, attempting to use a copied shape with Tickets resulted in a problem locating new entries in the Work Management Tickets landing page. This was an issue with the ticket details being embedded in the shape pages while the rule references that were created for the tickets in pyModifiers were not updated to match, and has been resolved by adding rule references for the tickets embedded inside the shapes.
SR-A97401 · Issue 265625
DASS validation can be switched from ERROR to WARN
Resolved in Pega Version 7.2.2
An enhancement has been added to allow optional switching of the validation of the column type mismatch to WARN as a save-time error/Guardrail warning instead of ERROR. This is based on the new DASS function 'reporting/validateColumnTypeMismatchAs', and the owning ruleset is 'Pega-Reporting'. Note : Even though save-time and run time validations are skipped using this DASS, the query may fail if the database does not support varchar and decimal comparison.
INC-139328 · Issue 588584
Corrected Excel table picture being included with the rich-text editor paste
Resolved in Pega Version 8.5.2
Corrected Excel table picture being included with the rich-text editor pasteAs an unintended consequence of code added to allow pasting or dragging and dropping an image for upload using the rich-text editor and the CK Editor, any copied content from Excel also added a table picture to the last cell as part of the pasted data. This has been resolved by updating the system to recognize content copied from Excel and prevent uploading of the image.
SR-A94493 · Issue 262430
JSON error resolved for empty section render
Resolved in Pega Version 7.2.2
While rendering a section, a JSON error was thrown in the console that prevented all click actions on the screen. Analysis showed this was due to an extra comma that was present when the page doesn't have any values, and has been fixed with a check that will only add the comma after DataPage scope after confirming the page is not empty.
SR-A91228 · Issue 258648
ConsiderLockingMode passed to GetNextWork
Resolved in Pega Version 7.2.2
When calling the OpenAndLockWork activity in the MoveToWorkList activity, the ConsiderLockingMode parameter was not being passed. This parameter value is checked to determine whether it is optimistic locking or not. To enhance the system, the First step of Assign-WorkList now sets the parameter ConsiderLockingMode to true/false based on based on the GetNextWork_MoveAssignmentToWorklist system setting so that optimistic locking is considered.
SR-A91228 · Issue 264407
ConsiderLockingMode passed to GetNextWork
Resolved in Pega Version 7.2.2
When calling the OpenAndLockWork activity in the MoveToWorkList activity, the ConsiderLockingMode parameter was not being passed. This parameter value is checked to determine whether it is optimistic locking or not. To enhance the system, the First step of Assign-WorkList now sets the parameter ConsiderLockingMode to true/false based on based on the GetNextWork_MoveAssignmentToWorklist system setting so that optimistic locking is considered.
SR-A89757 · Issue 258597
SaveAs history carries previous version and ruleset info
Resolved in Pega Version 7.2.2
When saving as a rule from particular version, the rule history did not correctly carry over the information about the origin ruleset version (Previous version and ruleset) This was an error caused by recent changes to the WBSaveAs record management API, and has been fixed with new parameters added to "call SaveAs" on Rule-!WBSave into the record management API.
SR-A87711 · Issue 255629
REST query key maps invalid characters to underscore
Resolved in Pega Version 7.2.2
When creating a REST Service with query key=value pairs that contains keys with dots/periods, the inbound mapping could not handle the keys and failed with an HTTP 500 error. To resolve this, changes have been made in the service API to locate any invalid character (according to ParameterPages) in a key to be mapped and substitute an '_' (underscore) character.
SR-A91327 · Issue 259570
Modified cookie name handling to clear operator sync between logins
Resolved in Pega Version 7.2.2
Full sync was happening only at the very initial time the user tried to login and not at every login, creating a scenario where an operator was given a synchronization package for the last logged user. This was an error with part of a session cookie name being hardcoded and not being cleared when the previous user logged out, and the logic has been corrected.
SR-A89757 · Issue 258099
SaveAs history carries previous version and ruleset info
Resolved in Pega Version 7.2.2
When saving as a rule from particular version, the rule history did not correctly carry over the information about the origin ruleset version (Previous version and ruleset) This was an error caused by recent changes to the WBSaveAs record management API, and has been fixed with new parameters added to "call SaveAs" on Rule-!WBSave into the record management API.