SR-B88923 · Issue 337768
Utility added to check for operators using default passwords
Resolved in Pega Version 7.4
To enhance security and ease of administration, a utility has been added that can disable default operators that ship with Pega Platform and Strategic Apps if the password hasn't been changed. This utility can be called as a service by PegaCloud. Please see the release notes for more information.
SR-D13880 · Issue 483331
Support added for using WorkPage class for FieldValue evaluation
Resolved in Pega Version 8.1.6
The Instructions provided under the Assignment details section of an assignment shape were not evaluating the FieldValue for the work object's audit history entries unless the field value was defined only at @baseclass. This was due to WorkPage class not being considered while evaluating a FieldValue, and has been resolved by modifying the InstructionsLookup control to use work class instead of the hard coded @baseclass.
SR-D6947 · Issue 444603
Email AttachmentPage updated to support use of Data-WorkAttach
Resolved in Pega Version 8.1.6
Attachments were not getting appended in the email sent by the Agent SendCorr. This was traced to a null Page that resulted if the attachment was of type custom Data-WorkAttach, and has been resolved by modifying the condition check on the objclass of AttachmentPage to change it from equalsIgnoreCase(Data-WorkAttach-File to startsWith(Data-Work-Attach-) .
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
INC-207996 · Issue 709663
Check added for parent case dependency if deferred-save is used
Resolved in Pega Version 8.6.4
After updating the status of a parent case to "Pending-ChildCaseDependency", the wait shape for the child case that should have been triggered by the status did not work and the child case remained on hold. This was a missed use case for the pxCheckFlowDependencies activity where defer-save operations on Index-AssignDeps class was not considered, and may happen when the Queue Processor is evaluating the dependencies while instances to Index-AssignDeps are not committed yet. To resolve this, code has been added to check the entry of the parent case dependency in deferred-save if its not present in Index-AssignmentDeps table.
SR-B88055 · Issue 342975
Parts Return process fires more than once when active
Resolved in Pega Version 7.4
The Parts Return process from Repair Order was not invoked for the second time even though the program configured on it was still active. This was traced to an Issue where multiple declare expressions that were fired when submitting the first repair order had an unintended side effect of calculating property values incorrectly, and handling has been added to resolve this.