Hello,
I’m working on configuring treatments (both web and SMS) in Pega, and the client has requested to include placeholders using fields from tables that do not belong to the primary context. I understand that this requires creating properties in the CDH-SR class, which would result in the columns being exposed in Cassandra and the pega_externalmkt database.
Is there a limit to the maximum number of such placeholders that can be added? If so, what is the recommended best practice for managing this?
Regards,
Francesca
@FrancescaI2720 When configuring treatments in Pega and including placeholders from tables outside the primary context it is important to manage the properties effectively. While there is no explicit limit mentioned for the number of placeholders it is crucial to follow best practices to ensure optimal performance and maintainability. Here are some recommendations: 1. Column Name Length: Ensure that the column names do not exceed 27 characters to avoid issues with database mappings. 2. Avoid Empty Rows: Make sure that the tables do not contain empty rows as this can lead to data integrity issues. 3. Mapping Properties: Properly map the properties to their corresponding columns in the external database. This can be done through the External Mapping tab of the class rule. 4. Database Table Instance: Create a database table instance to map your class to a database entity in the marketing schema. 5. Performance Considerations: Be mindful of the performance implications of adding numerous placeholders. It is advisable to only expose the necessary properties to avoid unnecessary overhead. By adhering to these guidelines you can effectively manage the placeholders and ensure that your treatments are configured optimally.
This is a GenAI-powered tool. All generated answers require validation against the provided references.
Optional: Extending communications holding class
Connecting to an external Cassandra database through a Database Table Data Set