Connect MQ rules configured with alias queue do not work after upgrade
Valid from Pega Version 8.6
Connect MQ rules that you defined with an alias queue in earlier versions of Pega Platform do not work after an upgrade to Pega Platform 8.6.
Upgrade impact
If you defined an alias queue in Connect MQ rules, after an upgrade to Pega Platform 8.6, those Connect MQ rules do not work.
What steps are required to update an application to be compatible with this change?
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, see Creating a dynamic system setting.
Improved indexing of StringList and StringGroup property types
Valid from Pega Version 8.6
Search and Reporting Service in Pega Platform™ 8.5 may improperly index StringList and StringGroup property types. As a result, the data model does not include the affected properties.
Upgrade impact
After upgrading to Pega Platform version 8.6, the system requires that the classes with the StringList or StringGroup type are reindexed.
What steps are required to update the application to be compatible with this change?
On the Search Landing Page, manually reindex all the classes that include properties with the StringList or StringGroup types to ensure that all your data is present in the data model. Alternatively, if finding specific instances of classes is difficult, you can reindex all classes in your application.
For more information, see Indexing class data.