Constellation - Business delegation

We have been asked to delegate data types, decision tables etc. as part of our on-going project. We are at 24.1.2.

Can someone explain the recommended way to delegate and let business maintain the same in Constellation?

@Salil good questions, glad you asked. It is very common for those coming from a Tradition UI background to jump straight back to delegating. In Constellation we have multiple ways of providing business users the ability to control data or rules inside of their apps.

Data

Constellation provides for the ability to allow you to “edit” data on any List View or Insight from a simple tick of the box. It further allows you to configure the create and edit views, which are far better than Traditional Delegation. The flexibility to use this in List Views or Insights and insert in the right context, give you further granular control to design the User Experience you want.

Check out:

Business Logic

In Traditional UI, you delegated the rule to a business user. It required you to teach someone how to edit each Pega Rule and in cases where a “feature” was multiple rules, you almost had to train them to be a System Architect.

In Constellation, and even in Traditional UI, you can utilise Configuration Sets to allow business users to control features in a simple and consistent way. App Studio further integrates into this, to allow you a low code authoring experience to insert this business logic into your Case Configuration or Rules.

If we go a little more technical, apart from the User Experience advantages, this also provides the ability to control configurations in multiple contexts, App level or Case Level. So in affect, a level of circumstancing to allow for multiple values and run time configurations, without the complexity of that concept for the business user.

Legacy Delegated Portal

That all said, it is technical feasible to bring back a delegation portal into Constellation. However, I would not recommend it, it isn’t just plug and play and I’ve seen some projects struggle to get this working. Even if you do implement it, the UX is not as good as options I mentioned, so my preference would always be above.