Which type of data is not typically part of a Correspondence Rule in Pega?

In Pega, a Correspondence Rule is primarily used to define how communication is managed within an application, such as emails, letters, or notifications sent out to users or stakeholders. The types of data that are typically involved in these correspondence rules include embedded page data, text string data, and case property data. Each of these data types helps to dynamically populate the content of the correspondence based on current case information or specific user details.

Embedded page data allows for the inclusion of structured data that is part of a more complex data object, while text string data provides the content that will be sent out, often including personalized messages. Case property data is essential as it pulls in information related to the case that triggered the correspondence, ensuring that the communication is relevant and accurate.

On the other hand, validation data does not typically play a role in the context of Correspondence Rules. Validation is more associated with ensuring that data inputs into forms or processes are correct and meet certain criteria, rather than being part of the correspondence communication itself. Consequently, validation data is not relevant when defining or managing correspondence, making it the type of data that is least associated with Correspondence Rules in Pega.