SR-B13418 · Issue 283237
Attachments removed when work object withdrawn
Resolved in Pega Version 7.3
After adding an attachment and then withdrawing the case, the unneeded attachments were still being stored in the attachments section until a refresh was performed. This was traced to code in the UpdateAndDeleteAssignments activity that appended the target page rather than replacing. This has been modified to ensure attachments are eliminated when the status of a work object is moved to 'Withdraw'.
SR-B16784 · Issue 287160
Attachments removed when work object withdrawn
Resolved in Pega Version 7.3
After adding an attachment and then withdrawing the case, the unneeded attachments were still being stored in the attachments section until a refresh was performed. This was traced to code in the UpdateAndDeleteAssignments activity that appended the target page rather than replacing. This has been modified to ensure attachments are eliminated when the status of a work object is moved to 'Withdraw'.
INC-175630 · Issue 653863
Application selections only announced when visible
Resolved in Pega Version 8.7
The elements of the application switcher were being announced by the NVDA screen reader even when toggled off, i.e. not visible. The issue was occurring because the focus was remaining at the search bar even after closing the app switcher window, and has been resolved by adding the necessary logic to switch the focus.
INC-195387 · Issue 681673
HandleResponses updated for use with optimized campaign
Resolved in Pega Version 8.7
After updating from Pega 8.4, responses were not processed in the pxHandleResponses Data flow if the "pyCampaignOptimization" flag was set to true. This was traced to a missed use case for an optimized campaign, and has been resolved by modifying the condition in HandleResponses.
INC-197530 · Issue 686027
Value Finder updated for use with external Cassandra nodes
Resolved in Pega Version 8.7
Attempting to use the Value Finder feature resulted in the error "Running Simulation is not possible because the required services are not available. Contact your System Administrator to enable the data flow and decisioning data store services." Analysis traced this to a check which identifies whether there is more than one internal node available for CDH/ DSS node. Since there were only external nodes available in this scenario and no internal nodes, the method returned false and returned the error when the CDH / VF page was launched. To resolve this, the check has been modified to allow for external Cassandra.
INC-174933 · Issue 651829
Special characters escaped for use in "is in List" lookups
Resolved in Pega Version 8.7
After creating a specific criterion on any proposition using a string property, the "Is In List" operator, and a customer list with one value containing a "$", clicking save or check in resulted in the exception error "Problem invoking function: pega_decisionengine_propositionfilterfua.pzPropositionFilterMethodBody--(PublicAPI,ClipboardPage) java.lang.IllegalArgumentException: Illegal group reference at java.util.regex.Matcher.appendReplacement(Matcher.java:857) ". This has been resolved by escaping regular expression control characters in string replacement, which will allow the use of characters such as the $ sign for "is in List" lookups.
INC-176757 · Issue 657785
Interaction History properly saved when running strategy on a different data flow
Resolved in Pega Version 8.7
Customized Interaction History properties that had been added to pyInteractionHistoryConfiguration and pyDefaultWorkingSet and saved into the PR_DATA_IH_FACT table were not being saved properly after upgrading from 7.3 to 8.3. This was a missed use case and has been resolved.
INC-173725 · Issue 656480
Logic updated for DX API retrieving View/Action ID using embedded property
Resolved in Pega Version 8.7
While calling the DX API using Assignment ID and action ID, a 500 error response was logged indicating that the server encountered an unexpected condition that prevented it from fulfilling the request. Investigation traced this to the logic used for resolving an embedded property referenced in a control/field to identify the correct page class. In a non-work object context for flow actions the new assign page doesn't exist, but the system was checking for it and clearing off errors from the named page. This has been corrected.
SR-B14774 · Issue 285008
Optional Process Child Case correctly sets ObjectClass
Resolved in Pega Version 7.3
When creating a Child Case from an Optional Process on the Case Type Rule, the ObjectClass of WorkPage did not update to the object class of the child case. The proper class was set when generated using an Automatic Process on the ObjClass. This has been corrected by using a performAssignmentCheck before acquiring work object.
SR-B14774 · Issue 285027
Optional Process Child Case correctly sets ObjectClass
Resolved in Pega Version 7.3
When creating a Child Case from an Optional Process on the Case Type Rule, the ObjectClass of WorkPage did not update to the object class of the child case. The proper class was set when generated using an Automatic Process on the ObjClass. This has been corrected by using a performAssignmentCheck before acquiring work object.