CDH :Context dictionary for multiple applications for same environment
Hello All,
I saw response from @Saleem_A few years back around this question, and we have been asked similar requirement so though of checking again, is this feature available soon? thanks
Pegasystems Inc.
GB
@RaviK6943 the enhancement request FDBK-61656 ( Allow multiple implementation layers built on PM) has not yet been integrated into the product.
Pegasystems Inc.
US
@RaviK6943As part of version 8.8, the next release, we are introducing limited support for such configuration to support small multi-brand and multi-country deployments. Depending on your use case, the 8.8 capabilities may help. This feature is not intended to support large scale deployments, so if your use case has 2 large "applications" then the recommendation continues to be to have 2 separate instances involved. The 8.8 feature is in early design so there is not full clarity on what will and will not be in scope just yet.
Areteans
AU
@Saleem_A Thank you very much for the details, the use cases ( Bank + Insurance) we known so far from Customer looks not large scale deployment but as soon as we get clarity we will post and get the confirmation.
Thanks,
Ravi
Pegasystems Inc.
US
@RaviK6943 , splitting this for Bank and Insurance seems an odd thing to do. Why would you not treat the customer holistically with one brain, instead of 2, one for each type of business line? Unless they consider the end customer to be a different entity between the business lines, you should advocate that they treat the customer as having the potential to be communicated to by the two business lines through one brain, and therefore one app.
Areteans
AU
Thanks @Saleem_A,
We are in the process of collecting business requirements to understand -->Unless they consider the end customer to be a different entity between the business lines.
In general I have few question w.r.to having both Banking and Insurance since both cases deal with distinct datasets in a single CHD instances
- Customer table would have data for both Banking & Insurance, how would ADM predictors will play here?
- From initial discussions, what if we want to support decisioning at Three levels i.e Customer(Group), Account(Banking) & Claims(Insurance) level - multi level decisioning, high level Context Dictionary could be following, but seems like this config is not supported ?
- Customer
- Account
- Associated Datasets
- Policy
- Associated Datasets
- Account
- Customer
Apology for not share the clear details around the requirements, next post, hopefully I will try to provide more clarity.
Thanks,
Ravi
Pegasystems Inc.
US
> Customer table would have data for both Banking & Insurance, how would ADM predictors will play here?
Yes. I would imagine many of the properties to be common between the two, and those that are not will just be blank. Predictions for banking actions will likely identify banking properties as relevant and same for insurance. This should not be an issue.
> From initial discussions, what if we want to support decisioning at Three levels
I'm not sure how/why this relates to Banking / Insurance apps discussion. This seems like a general question about multi-level. Please break this out into its own question so its not lost in discussion on multiple applications. If this is indeed related to multiple apps, please clarify the question accordingly.