INC-200802 · Issue 699965
Line break handling added for setting required question asterisk
Resolved in Pega Version 8.5.6
If a survey question was formed in multiple sentences, the asterisk marking it as required was not displayed in screen. The asterisk displayed as expected if the question was one sentence. This has been resolved by updating the setMandatoryIconforQP script handle linebreaks and set the required symbol as expected.
INC-200936 · Issue 703345
SFTP support added to ValidateURL rule
Resolved in Pega Version 8.5.6
SFTP has been added to the list of schemes which are accepted as part of the validation in the pxValidateURL rule.
INC-202562 · Issue 701629
Updated FieldLevelAuditing logic for page comparison
Resolved in Pega Version 8.5.6
Optimistic locking was resulting in orphan assignments and the error "Error: Flow Not At Task, Error: Flow Removed". In addition, Get Next Work was causing duplicate Field Level Auditing records. This was traced to a missed use case in the logic used in pxFieldLevelAuditing where previousPage and PrimaryPage are compared to see whether they are equal or not, and has been resolved by adding one more condition to mark previousPage as null when the update date time or commit date time are not updated as part of processing.
INC-202943 · Issue 700195
WorkLink URL generation updated for security
Resolved in Pega Version 8.5.6
When using a WorkLink in an email, clicking the link and entering credentials on the login screen resulted in a 403 unauthorized error. This was due to a WorkLink URL generation issue caused by the non-encryption of the RedirectAndRun activity call in the URL, and has been resolved.
INC-204676 · Issue 699111
Localization added to subject line for SendEmailToAssigneeOnGoalTime
Resolved in Pega Version 8.5.6
When a Callback case was created and the assignee notified by email, the subject line was not localized. This has been corrected.
INC-207218 · Issue 706370
Check added to prevent duplicate approval by single agent
Resolved in Pega Version 8.5.6
When using a cascading Approvals process supported both by a web access button or by responding via email, a single agent could use both methods and advance a case an additional step as if they were the next approval level. This was due to the system only checking the pzInsKey when processing the approval while the assignment key will be the same for the cascading approvals assignments. This has been resolved by introducing a datetime check to validate if the email approval assignment creation datetime and the one in the database have same value; if yes the approval process will proceed and if not it will exit.
INC-135335 · Issue 588510
Parent flow next step will take precedence over sub-process
Resolved in Pega Version 8.5.1
A Breadcrumb configured in the screen flow was not displaying at the last assignment when there were multiple embedded sub processes and the last assignment was called in a sub process. This was traced to the parent flow next step information not being passed due to the next step in the sub process being marked as an end shape. To resolve this, the pzFlowSteps7 html control has been updated to pass the parent flow's next step information in this situation.
SR-D77719 · Issue 569769
OpenIfStale updated to resolve optimistic locking race condition
Resolved in Pega Version 8.5.1
A race condition was created in optimistic locking by having two assignments save at overlapping times. This has been resolved by modifying the pzShowConflicts activity to use a version of openIfStale which will consider a workpage as stale even if the difference in pxUpdateDatetime is in milliseconds.
INC-134912 · Issue 581326
Handling updated for wait shapes with different outgoing connector flow actions
Resolved in Pega Version 8.5.1
After configuring a flow with a wait shape that by default used the pyContinueAfterWait flow action for the outgoing connector of the wait shape refer, adding any other valid flow action resulted in the error "Action To Take must be a valid flow action for this assignment". This was due to the post-processing of the connector properties modal updating the ActionToTake value based on wait shape, so that changing the flow action on a connector caused the validation on save to fail if the ActionToTake on wait shape and the connector flow action did not match. To resolve this, the system has been modified to validate a wait shape with different flow action on the outgoing connector.
SR-D59283 · Issue 523207
Check added for WorkParty property to catch changes
Resolved in Pega Version 8.5.1
After configuring a send email shape to send email to work parties, proceeding through the flow without work parties and then triggering the send email shape and creating the Fix correspondence assignment worked as expected. If the work party details were later updated and the send email shape was triggered again for the Fix correspondence assignment, the error message "No role defined to work object" appeared. This was an issue with the handling of the email flow the second time through: PyCorrPage.pyCorrPartyRole did not have the work object party details which were added to the work object after the fix correspondence assignment was created, and SendSimpleEmail was not designed to handle the email that needs to be retried during the FixCorrespondence flow call. To resolve this, the system will check whether the pyWorkParty property exists prior to calling the PartyCorrPreferences HTML rule.