To improve the guardrails compliance score of an application, you can perform the following actions:
Ensure keyed data classes are not mapped to pr-other where possible:
Pega recommends avoiding the use of the pr_other table for keyed data classes as it can lead to performance issues and complicate data retrieval.
Instead, ensure that keyed data classes are mapped to dedicated tables. This enhances data management and improves compliance with Pega's best practices.
Convert activities that only retrieve data to data transforms that invoke data pages:
Activities in Pega can be complex and harder to maintain. When activities are only used to retrieve data, it's better to convert them to data transforms that call data pages.
Data pages are reusable and declarative. They help in maintaining consistency and reducing the complexity of the application.
Reference:
Pega Documentation on Data Classes: Data Classes
Pega Documentation on Data Pages and Data Transforms: Data Pages