Configuration Set - Decision table

Hi,

I have created a Configuration Set with Decision table as a source. When I check in Administration landing page from Manager portal, configuration set is displayed as read only field with text “CALCULATED”.

image

Manager AccessGroup has “PegaRULES:WorkMgr4” and “PegaRULES:EditConfigTable” Access roles.

Glad to see Config Sets in use :clap:

I remember this one but can’t find my notes on the exact cause. So my guess in likely order:

  1. Decision table is still in branch (not merged so user doesn’t have access)
  2. Decision table is not marked as relevant record (so run time Constellation can’t see it)
  3. Decision table is marked relevant but its stuck in a branch (doesn’t merge with merge wizard)
  4. Application doesn’t have a production ruleset (decision table is a rule so it needs to go somewhere)
    1. See Technical considerations for Configuration Sets
  5. End user doesn’t have access to production ruleset (in access group settings)

Have a look if any of those applies to you? I’d recommend raising a Support Ticket to get this investigated.

Hi Marc,

Thanks for the reply.

Decision table is not in branch and it’s marked as relevant record.

Saved the decision table in Production ruleset and production ruleset is present in both application and user access group.

I am not sure to raise a Support Ticket as I am using Pega VM instance.

If you found your notes, please do let me know.

@Surya_Sagar
Can you check if the Configuration Set’s definition?

If the setting uses “Calculated value from decision table” it intentionally becomes read-only in the Admin UI because its value is derived at runtime. The Manage page shows “CALCULATED” rather than letting you edit the value inline. This is expected when the default/value is driven by a decision table.

Hi @RaviChandra Yes, I have configured as “calculate Value from Decision table” .

I have a use case that business user has to update the decision table. If Configuration Set is designed to be read only for decision table. Is there any other way in constellation to update the decision table by Business user?

@Surya_Sagar You CAN let business users update decision logic, but when a Configuration Set uses “Calculated value from decision table” the setting shown as “CALCULATED” is expected because the value is derived at runtime.

You can try to-

  • Delegate the decision table to business users (recommended)
  • Keep the decision table as the calculated source but expose a business-editable configuration layer
  • Use delegated rules + governance if you need more freedom

I’d recommend you to keep it simple and delegate the decision table and let hte Configuration set be used for dynamic population of the calculated value.

You don’t need to delegate the decision table, Configuration Sets is the replacement for Delegation of rules. (Just like CRUD actions on data is replacement for delegated data)

There is something wrong here with the configuration - there should be a link in the Config Set screen for editing the decision table.

@Surya_Sagar did you create the decision table using Configuration Sets in App Studio? I vaguely remember dev studio ones not being available here - so that can also lead to it being read only.

The Design Time UX is not so great, maybe you forgot to click the gear icon?

Hi Marc,

I have created the decision table from Dev Studio and marked as relevant record. If the context is changed to case type, the decision is available in dropdown and selected from there.

I have also tried creating new decision table from Configuration set. But still same result.

This is what it should look like

This one is annoying me because I know I encountered this years ago but can not find any notes on what we did to fix it. I’ve also trawled just about every resource public and internal, and can’t find anything on the topic sorry :frowning:

Please let me know the INC number, I would like to follow along.

I couldn’t raise a Support Ticket as I am using Pega VM Instance.