For Microsoft SQL Server deployments, change settings to create data types in Integration Designer
Valid from Pega Version 8.1
For on-premises deployments that use Microsoft SQL Server, set the Pega-Reporting/reporting/useMergeHintForRRquery dynamic system setting to true. If you do not configure this setting, you might not be able to create a new data type in Integration Designer that uses Pega as the system of record. Configure the setting as follows:
- Owning ruleset: Pega-Reporting
- Setting purpose: reporting/useMergeHintForRRquery
- Value: true
For more information about configuring dynamic system settings, see Creating a dynamic system setting.
Data entered in a new harness is lost after a sync operation
Valid from Pega Version 8.1
If you create a case in an offline-enabled application and enter data in a new harness, this data is lost after you click Offline capability and Enabling offline support for cases.
and the sync operation takes place. For more information, seeRule revalidation after updating properties without restarting nodes
Valid from Pega Version 8.2
When you update certain property attributes, such as a property's maximum length, rule types that reference the property might not reflect the change. You do not always have to restart nodes to revalidate the referencing rules when they cannot be resaved, for example, when they are in a locked ruleset. For Pega Platform™ 8.1 and later, for non-stream rules, such as activities, data transforms, and so on, use the reassemble API in Admin Studio or truncate the assembled classes table.
For stream rules, such as sections, harnesses, paragraphs, and so on, reassemble the rules and restart the nodes. For more information, see More about properties.
For previous versions of Pega Platform, use the System Management Application (SMA) to revalidate stream and non-stream rules.