Decision Consultant Course Place to apply engagement policy

General
, , , , ,
1

Hi

I am going through the decision consultant course and I was following this exercise-

Here the eligiblity criteria was



Action

Type

Condition: Customer…


All credit cards

Eligibility

is at least 18 years or older

However in the video it is applying the Eligibility criteria in the Customer Action context. May know the reason why it is being added to Customer context and not on all action context of Eligibility criteria.

Thanks

2

@kaushikd4494

Hello,

Great question! The eligibility condition you mentioned belongs in the Customer context because it depends on customer attributes rather than the action itself.

Here’s why:

  • Customer context: Eligibility rules that evaluate customer-level attributes (age, location, segment, etc.) belong here because they’re independent of any specific action. When applied here, they determine whether the customer qualifies for any action.

  • Action context: This is used when eligibility depends on attributes of the action itself (product type, offer validity, channel availability, etc.). For example, “The action is only available in the mobile channel” would be an Action-level condition.

In your example, requiring the customer to be at least 18 years old is a universal requirement for all credit card actions. Since it’s based on the customer’s age, it should be defined in the Customer context. This ensures consistency and avoids redundancy—otherwise, you’d need to repeat the same condition for every action.

Hope this helps! Let me know if you’d like more details or examples.

– Nick

3

@carln

I have another question:

With reference to Strategy Result class from below link

We can extend any application related properties in SR class which is direct inheritance to pxStrategyResults class, however in our application all strategies are created in pxStrategyResults class. Kindly suggest how to use application related properties in SR class in our strategy.

4

@kaushikd4494

You want to use custom properties in strategies that currently reference pxStrategyResults. Here’s the recommended approach:

  1. Create an SR class in your application layer that directly inherits from pxStrategyResults.
  2. Add your application-specific properties to this class.
  3. Update your strategies to reference this SR class in their configurations using the Strategy Result Class setting (see Pegasystems Documentation for details).

By doing this, your strategies will have access to both OOTB and application-specific properties.

If you can’t change the Strategy Result class, try these options:

  1. Use Property-Set components in the strategy to populate application-specific properties from the primary context (e.g., Customer or Interaction class).
  2. Leverage Data Transforms post-strategy execution to enrich the results with the properties you need.

Best Practice: Always keep custom properties in an application-specific SR class for maintainability and upgrade safety.

I hope that answered your question! Let me know if you need more detail or if you have further questions!