NBA Pega Marketing Engagement Policy for pages inside primary context
We have a strcture of Customer (primary context) and child classes like Account, Credit Card.
We defined the Engagement policy with some conditions in the Customer context, also in the Account and Credit Card context.
However, when I run the proposition filter, it seems like no condition is met. But, the customer has the criteria to be elegible and met it.
If you know why is not met the criteria please, let me know. I've been thinking it would be it because of the implementation using "Accounts includes an instance where EstatusCuenta1o3". Should we use another kind of approach for implementing conditions on properties inside of page in another context?
I attached you the proposition filter, the fake customer profile, and the first when rule.
***Edited by Moderator Marissa to update Content Type from Discussion to Question***
It sounds to me like you have built this correctly. Could the problem be how you are testing this? I'm not sure that the Proposition Filter record would be able to give you the correct result. You may need to test this in the context of a Strategy. Have you tried this?
Also, are you sure that the Engagement Policy is not working due to the "instances includes" criteria? Have you tested that in isolation?