Relevant Record Migration in Constellation

General
, , , ,
1

Hi Team,

In a Pega Constellation application, I’d like to confirm the scenarios in which a rule is automatically marked as a Relevant Record.

Are the following scenarios correct?

  1. Creating a rule directly in App Studio

  2. Creating a rule through Case Life Cycle design in Dev Studio (e.g., configuring a view in a data collection step)

  3. Creating a rule in the Data Model via Dev Studio (e.g., adding a field/property to an existing data type)

Are there any other scenarios where rules are automatically marked as relevant?

Also, when moving code from one environment to another:

  • If a rule is automatically marked as a Relevant Record (based on the scenarios mentioned above), do we still need to include the Relevant Record instance in the product rule manually?

    Or do we only need to include Relevant Record instances in the product file when we manually mark a rule as relevant?

  • In short, for both automatically and manually marked relevant records, do we need to explicitly include the Relevant Record instances in the product rule to ensure they are recognised as relevant in the target environment after migration?

Thanks in advance for the clarification.

2

@AchinthaJ Yes, in Pega Constellation, rules created directly in App Studio, through the Case Life Cycle (like views in data collection steps), or by adding fields in the Data Model (even in Dev Studio) are automatically marked as Relevant Records. Other cases like adding fields or relationships in App Studio also trigger this. But when moving code between environments, these Relevant Record tags are not included automatically. Whether a rule was auto-marked or manually marked as relevant, you still need to include the Rule-RelevantRecord instances explicitly in your product rule. If you skip this, the rules may not appear properly in App Studio after migration, even though they technically exist. So always package the relevant records to preserve proper behavior in the target system.

3

Thank you @Sairohith