Global Control Parameters Customer Class vs Proposition Landing Page
I have noticed in applications on clients I have seen Global Control Parameters being defined on on the proposition management landing pages within the context of group/issue. The lesson however stresses that it should be defined on the customer class. Can this be clarified? Is it appropriate to create them on the landing page in the context of group/issue if they do not deal with customer properties. Thank you.
Are you working through a particular course on Pega Academy? If so, what course and version? Providing this information will help us answer your question. If your question is not related to a PA course, try posting it on the Ask Pega Support Community.
I was doing the exercise in the "ADAPTING TO BUSINESS TRENDS USING GLOBAL CONTROL PARAMETERS" 7.22, The exercise uses customer credit scores. I wanted to use the exercise as a guide to implement GCP using a count or inventory attribute/property of an offer. Since that would be a property belonging to the class of the offer vs the customer would it be implemented differently than in the exercise?
It is a very good question. First of all, you might have seen people 'misusing' what we call proposition control parameters by implementing them as regular proposition properties and changing them on the proposition landing page. We do NOT advice this approach.
The 'proper' way to implement proposition control parameters (PCP), which is unfortunately NOT the scope of the GLOBAL control parameter (GCP) lesson, is to implement them as decision data rule (similar to GCP) but the apply to class being the proposition SR class. And then you import them on to the canvas, and you use a data join to join the properties with the propositions.