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.
SR-122809 · Issue 182677
Application Wizard updated to use long-form function name
Resolved in Pega Version 7.1.8
When using the Application Wizard in some environments, clicking 'Preview' or 'Create' on the Data Objects screen caused a refresh and no summary of the created rules was generated. This issue was traced to an error in the library/function rule resolution where the short-form reference to a function was finding more than one suitable rule resolution candidate if there was more than one version of a ruleset function with the same formal parameters and the function was called using the short form of the function name. In this particular scenario the PageListContains function was causing a problem as this function exists in both the PegaSurvey framework and the Pega-AppDefinition ruleset. There was a workaround of doing a private checkout of the CopyFrameworkClassGroup activity and changing the short function rule reference to the long function rule reference (specifying ruleset and library, but the Wizard has been updated to use long-form function name to prevent this issue.
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-121825 · Issue 181670
Multiple annotations now allowed for swimlane objects
Resolved in Pega Version 7.1.8
When two annotations were used with swimlanes, the description in the annotation is unexpectedly changed or the annotation itself disappeared due to an ID conflict. There was a workaround of adding the shapes using the right click, but the annotation shape is now correctly added to the work flow using the proper unique ID.
INC-191356 · Issue 679163
External Input setting available on Strategy Batch Performance Test
Resolved in Pega Version 8.7
It was not possible to specify the External Input as part of a strategy when using a Batch Performance test. This has been resolved by updating the pzDisplayTestStrategyContext When condition to "true" the so external input selector is properly displayed.
SR-127961 · Issue 192637
Corrected reference name for doc attached to work object by CreateMergedWordDoc
Resolved in Pega Version 7.1.8
When using the CreateMergedWordDoc flow action to create a document and attach it to the Work Object, the display showed the label used in "pyNote" as the document name. However, opening the document opens it under the category name. This was caused by a mismatch in the handling and has been corrected.