Best practice for Offer Catalogue management
Dear Community,
We are looking for the best practice for Offer Catalogue management.
Our client has 2 teams working with the PEGA 7.3.1 platform:
- Business Team is working in an agile mode performing offer changes within 1-2 hours. Environments used: UAT -> PROD
- Delivery Team is working on projects (like new integration) within few days to few weeks. Environments used: DEV -> SIT -> UAT -> PROD
The agility of Business Team is a must, processes and technical solutions should be tailored by this principle.
Questions:
Question #1: Both Business Team and Delivery Team are changing offers (independently from each other) but these need to be merged. What is the best practice for updating the Offer Catalogue in this context? Which should be the environment for the code merge? What should be the process steps to merge the 2 teams’ Offer Catalogues?
Question #2: Is it possible with 7.3.1 to update few offers only and not the entire Offer Catalogue?
Thank you.
***Moderator Edit-Vidyaranjan: Updated SR details***
Pegasystems Inc.
GB
Hey Mohit,
Can't see your profile but I think we meet in Dubai a while back? If so I hope you are well.
With reference to your questions, I would need a little more information to make sure we are talking about the same thing.
When I look back at my notes offers were propositions, are you talking about propositions or offers? If you are talking about propositions are you using un-versioned or versioned propositions?
If you are using versioned propositions then an option for you to manage this is to use Revision Management which is Pega's change management tool for business led change. To utilise this you would likely need to make some changes to your operating model and to assess the suitability of your Business Issue / Group heirarchy. Last time I referenced your logic it wasn't very finely grained which would perhaps make separation of concerns harder.
Start off by having a look at this tutorial and follow the links to documentation and academy training
Hey Mohit,
Can't see your profile but I think we meet in Dubai a while back? If so I hope you are well.
With reference to your questions, I would need a little more information to make sure we are talking about the same thing.
When I look back at my notes offers were propositions, are you talking about propositions or offers? If you are talking about propositions are you using un-versioned or versioned propositions?
If you are using versioned propositions then an option for you to manage this is to use Revision Management which is Pega's change management tool for business led change. To utilise this you would likely need to make some changes to your operating model and to assess the suitability of your Business Issue / Group heirarchy. Last time I referenced your logic it wasn't very finely grained which would perhaps make separation of concerns harder.
Start off by having a look at this tutorial and follow the links to documentation and academy training
For help with implementing revision management and any changes you would need for this to work (such as migrating from versioned to unversioned proposition or changing your operating model to utilise this capability) I suggest you contact Pega Consulting or people in your organisation with experience of this feature.
I have also attached a deck which has the roadmap at the front but at the end is a section which has an introduction to revision management which you may find useful.
Cheers, Alex
Accenture
AE
Hi Alex,
Glad hearing from you, thank you for the response. Please find below some clarifications:
“When I look back at my notes offers were propositions, are you talking about propositions or offers?”
We use Propositions.
“If you are talking about propositions are you using un-versioned or versioned propositions?”
We use Versioned Propositions.
“If you are using versioned propositions then an option for you to manage this is to use Revision Management which is Pega's change management tool for business led change.”
We are already using Revision Management.
“For help with implementing revision management and any changes you would need for this to work (such as migrating from versioned to unversioned proposition or changing your operating model to utilise this capability) I suggest you contact Pega Consulting or people in your organisation with experience of this feature.”
You mentioned above migrating from Versioned to Unversioned Proposition. Is that making possible to update few Propositions only and not the all the Propositions in one shot?
Thank you.
Pegasystems Inc.
GB
Accenture
AE
Hi Alex,
Yes we can add the group in the CR. But if we select one or two proposition in the CR created only the selected proposition will be added in the new version and rest will be discarded. Strategy will import the proposition only from higher version i believe and not all.
Let me know if I am wrong.
Thanks
Pegasystems Inc.
GB
Hi Thomas,
That is not how it should work at all, is that how it is happening with you? If it is please raise and SR.
The purpose of selecting a proposition as part of the CR is that we are editing that row of the DD rule. Other propositions will still be present and will not be discarded.
Cheers, Alex
Pegasystems Inc.
IN
Hi Thomas,
Alex is correct, it should not discard previous propositions. But while the user is working on CR, the decision data he will only see propositions/offers that are included in the CR. But the strategy will import from original decision data which contains all propositions.
Hi Thomas,
Alex is correct, it should not discard previous propositions. But while the user is working on CR, the decision data he will only see propositions/offers that are included in the CR. But the strategy will import from original decision data which contains all propositions.
Thanks & Regards,
Matta
Pegasystems Inc.
US