Relevant Record Migration in Constellation

User Experience
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

@AchinthaJbefore taking a deeper dive please take a look here to check if it answers your question: Deployment of associated objects | Pega Community

3

Thanks for the article, @Kamil Janeczek. I think I got the answer from it, please correct me if I’m wrong.

Regardless of whether a rule was marked as a relevant record automatically or manually, in both cases we still need to manually move or deploy the underlying relevant record instance of that rule to the target environment in order for the rule to be marked as relevant in the target environment. Is that correct?

4

@AchinthaJ That is correct

5

Thank you @Kamil Janeczek