INC-168253 · Issue 652547
Documentation updated for using Connect MQ with clustered queues
Resolved in Pega Version 8.7
After update to Pega Platform v8.6, an issue was seen with Connect MQ rules that used an alias queue. The support documentation has been revised to outline the necessary steps for updating an application to perform as expected. In the Pega-IntegrationEngine ruleset, create the following dynamic system settings and their default values: "mq/pmo" = 0 "mq/gmo" = 0 "mq/oo_request" = 1040 "mq/oo_response" = 16 For more information, dynamic system setting support articles are available.
INC-182959 · Issue 668737
SQL queries modified to use qualified table references
Resolved in Pega Version 8.7
Portal launch in the development environment was taking an excessive amount of time, as were some standard reports. The PurgeAssemplyDatabaseCache agent activity also generated an error regarding "(internal.cache.RAPurge) ERROR - Purge, unexpected error in removeOldAppCentricCacheData". These issues were traced to SQL queries that contained pr_sys_app_hierarchy_flat without a schema qualifier, and have been resolved by changing to class qualified table references.
INC-185760 · Issue 668742
SQL queries modified to use qualified table references
Resolved in Pega Version 8.7
Portal launch in the development environment was taking an excessive amount of time, as were some standard reports. The PurgeAssemplyDatabaseCache agent activity also generated an error regarding "(internal.cache.RAPurge) ERROR - Purge, unexpected error in removeOldAppCentricCacheData". These issues were traced to SQL queries that contained pr_sys_app_hierarchy_flat without a schema qualifier, and have been resolved by changing to class qualified table references.
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-190130 · Issue 678541
Help information updated for using Elastic Search with Report Definition
Resolved in Pega Version 8.7
The support article "Configuring a report definition to run against an Elasticsearch index" has been updated to clarify that the search can pass multiple values with a space in pySearchString as it does OR operation on all the fields, and that filters in the report definition will be used when executing the report directly or when calling the report in the pxRetrieveSearchData activity. https://community.pega.com/knowledgebase/articles/system-administration/85/configuring-report-definition-run-against-elasticsearch-index
SR-C57557 · Issue 402534
Work Object lock released correctly when modal dialogue is canceled
Resolved in Pega Version 8.2
The Work Object lock was not being released when the modal dialogue cancel button was clicked. This was due to the primary page not being switched to the pyWorkPage during the cancel, and has been fixed.
SR-C79205 · Issue 416399
OnChange event only triggered on date field when value changes
Resolved in Pega Version 8.2
After configuring the onchange event for a date control field with some action, clicking on the Date picker option and selecting the same date triggered the onchange even when the value had not changed. This has been resolved by updating the code to store the previous value and check for a value change before firing the change event.
SR-C73994 · Issue 415479
OnChange event only triggered on date field when value changes
Resolved in Pega Version 8.2
After configuring the onchange event for a date control field with some action, clicking on the Date picker option and selecting the same date triggered the onchange even when the value had not changed. This has been resolved by updating the code to store the previous value and check for a value change before firing the change event.
INC-162122 · Issue 633066
Create modal is accessible when creating case from Create menu
Resolved in Pega Version 8.5.4
After creating a new case in the Cosmos User Portal, the “Create” screen Modal Dialog opened but focus did not move to any element within the modal dialog but instead stayed on the “Create” button on the left side menu of the User Portal. It required approximately 50 tabs to reach any actionable element within the modal dialog. Investigation showed that the create modal launched the section in an AJAX container that looked like a modal, but the focus was not being correctly set on the first element. This has been resolved by ensuring there is a focusable element when launching an AJAX container.
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.