Posted: 25 May 2020 9:56 EDT Last activity: 31 May 2020 21:25 EDT
Decisioning on externally hosted propositions
How can one perform decisioning on propositions hosted outside Pega? Say, the business has a catalogue management system which allows users to add/ modify/ withdraw catalogues. These catalogues have to be used by the decisioning system to generate offers. How does this requirement fit into Pega’s decisioning capabilities?
I have thinking along the lines of having a background process load these catalogue items once a day as unversioned propositions into Pega. This data can then be used in strategies to choose the right proposition for the customer.
I did come across a couple of articles that spoke about phasing out unversioned propositions. If this feature is removed, then what’s the optimal design to convert such external items into decision-able propositions?
You are correct that un-versioned propositions are not supported. Why do you wish to use them instead of versioned propositions in the same manner you highlight? Is this a comms use case? If so, I believe the comms framework has a patterns in place for achieving this requirements.
I would love to make use of versioned propositions to load the external catalogue items thereby converting them into propositions. Given that these are versioned rules, I have to create a background processes who’s job would not be a simple ETL from one table to another rather be smart enough to play with ruleset versions in which the decision data rules fall into (Since versioned propositions are maintained in decision data rules).
Now, before I think of a way to achieve that, am I thinking the right way? Is there an API that Pega offers OoTB to convert the result set of a query into contents of a decision data rule?
Also, what’s a comms use case? Can you guide me towards any documentations that talk about this use case?
Like I mentioned in my closing, I suggest you consider if Pega already had patterns implemented for this, which I'm pretty sure they do for Comms vertical (please confirm that this is for comms vertical).
Having said that, the pattern you call out is correct. You call and API to manage the rule, you iterate through your external data source records and call an API updated the rule and then call an API to confirm it's completion. The reason I highlight that you should review comms vertical is that this would all be in place instead of having to build it yourself.
When you say Comms vertical, are you talking about Pega Marketing for Communications? If so, yes. That’s the product am working on. Having said that, could you share a bit more specifics on this API that you are referring to? That information would really be handy.
Thanks in advance,
Posted: 11 months ago
Updated: 11 months ago
Posted: 31 May 2020 21:24 EDT Updated: 31 May 2020 21:25 EDT
Thanks to Saleem, I was able to find the product - Pega Foundation for Communications. By the looks for it, I can see that this product allows us to create Product Offerings, Product specifications and much more. This can then be used to create offers in the product - Pega Marketing for Communications.
Am yet to implement this, but I think this is probably a solution to my original post.