SR-B7355 · Issue 277915
Actions visible in Perform harness for cases without active assignments
Resolved in Pega Version 7.3
When a stage configured with SLA did not have any active assignments, local actions could be launched from the Review harness but were not visible in the Perform harness. This was caused by the handling for cases without active assignments: virtual assignments are used to process the stage/case wide local actions, but the name of the virtual assignment page was not set and therefore not available later to fetch the local/flow actions. To resolve this, the assignment page name will be checked and set if it is empty.
SR-B7620 · Issue 290018
PopulateCaseContents activity updated
Resolved in Pega Version 7.3
The PopulateCaseContents activity has been updated to better handle missing or empty properties to ensure the flow name and RefObjectClass values are populated properly.
SR-B7621 · Issue 278634
Activity created cases open correctly
Resolved in Pega Version 7.3
When a case was created through an activity, an error was generated when opening the case and clicking to open assignment. This was traced to an incorrect page name being passed if the primary page was different, and has been resolved by modifying the CompleteAssignment activity Step 19 to check the precondition of Page name.
SR-B8696 · Issue 279855
Support added for FCM GetNextWork
Resolved in Pega Version 7.3
When using Federated case management (FCM) to get next work, the work object pulled was not assigned to the operator. This was due to the implementation of FCMR not supporting the moving of workbasket assignments to worklist through get next work. To support this use, the following functions now accept extra parameters as last param: FCMRGetNextWork FCMRGetNextWorkItem FCMRProbeNextWorkItem This will enable distinguishing between normal GNW and federated GNW, and it is possible to override any py rule call MoveToWorklist.
SR-B9998 · Issue 279141
Improved handling for apostrophe in email addresses
Resolved in Pega Version 7.3
In order to improve mail handling, the system will now only remove the the starting and ending apostrophe in an Email address and will not strip apostrophes in the middle of an address.
INC-138348 · Issue 599772
Added parameter skipPropertyEvaluation to handle CSS in email HTML
Resolved in Pega Version 8.4.4
While sending an email with custom HTML appended to the email body, a "+" sign in the body was causing the correspondence generation to fail. Investigation showed that if there were CSS classes with braces in the message body, the braces were being removed and replaced via "+" symbol in step 21 of CorrCreate activity. To resolve this, a new Boolean parameter skipPropertyEvaluation has been added in the CorrCreate activity to handle the decision to either evaluate the logic or not, and the pre-requisite will be to resolve all the property references before calling this activity so custom CSS braces { } will be honored when the message body is sent.
INC-140266 · Issue 602076
Search made consistent across environments
Resolved in Pega Version 8.4.4
Search was behaving differently based on whether the user was launching the search by clicking the search icon or hitting enter directly. The search icon passed the classes list and fetched cases based on that, whereas hitting enter performed the search without the classes list unless it was a multi-tenant environment. This has been resolved by updating the pyWorkIDSearch activity to pass application classes list in any environment.
INC-143025 · Issue 600611
API performance improvements
Resolved in Pega Version 8.4.4
Performance improvements have been made for running the get assignment action details API.
INC-144265 · Issue 609287
Updated timestamp handling for duplicate key issue with PyCompleteAutomation
Resolved in Pega Version 8.4.4
Occasionally a robot failed to complete a case due to a duplicate key exception. This was an issue with the History record creation due to duplicate key erlated to the timestamp, and has been resolved by updating the timestamp handling so that the REST API will use 'getCurrentTimeStampUnique' and for other cases 'pxGetCurrentTimeStampThreadUnique' will be used.
INC-144358 · Issue 601014
Localization added for "Automatically" and "Manually" field values
Resolved in Pega Version 8.4.4
The Dutch translation of "Child case [Case_type] [Case_id] has been [Instantiation_mode] instantiated" used the hard-coded English expression "manually". This has been resolved by adding the "Automatically" and "Manually" field values to localization.