Best Way to store catalog approval group

[SwarnadeepNandy]

We are having multiple catalog items and we have flows associated per catalog item for approval and task creation. Now approval group for each catalog item is stored in the flow (which for me seems to be hardcoded). Anytime we need to make changes in the approval group (due to group split, expansion geographically etc) we have to change the groups manually in the flow.

So does, ServiceNow have any better solution for this, where we can store the approval groups for the catalog items in more generic way?

For eg: store the approval group in the catalog level (I found a field called fulfillment group at the catalog level) or any OOTB table where this configuration data can be stored and fetched at runtime using the flows.

Thanks in Advance,

Swarnadeep Nandy

[Allen Andreas]

Hi,

This is a perfect example for using decision tables. Documentation here: https://docs.servicenow.com/bundle/rome-servicenow-platform/page/administer/decision-table/concept/d...

Please mark reply as Helpful/Correct, if applicable. Thanks!

[Allen Andreas]

Hello,

I'm unsure if you saw my reply since you only responded to one person, but feel free to review my reply or let us know if this wouldn't help....?

Please mark reply as Helpful/Correct, if applicable. Thanks!

[SwarnadeepNandy]

Hi Allen,

Yeah, saw your reply definitely. I was Checking on the Decision table concept and in context of our use-case, if it would be helpful or not.

What I found that decision table is capable of much more and there we can put operations to receive a result. What I feel is, Decision table is really a powerful element, but if I try to use decision table for our use-case, it will be overcomplicating.

For me a field (for eg: approval_group) on the catalog item table could have been the best solution, if not field an matrix table would also work fine.

Because if I try to put this data into decision table, it can be become very complicated to maintain for a non-technical person. And moreover fetching the result from the table is bit complicated as we need to use the decision table api and parse JSON (I know, similar has to be done if we are using matrix table, but still familiarity remains a question.)

But definitely, the concept is very useful and powerful, and it needs proper use-case to fit in.

Best Regards,

Swarnadeep Nandy

[Allen Andreas]

Hi,

One of the main selling points to decision table is the citizen development possibility and it's no code interface. You can give them permission and the one of the major use cases is for them to maintain it. So that's quite funny you feel it's overcomplicated for a non-technical person.

The result is easily pulled via flow designer. Perhaps that's for San Diego specifically for that feature versus Rome, but I would recommend checking it over again sometime.

In any case, it sounds like you already know what you want to do, so I'll leave it at that. My apologies if my reply was not Helpful, but on the flip side, what you mentioned is exactly one of the use cases for it, in my opinion anyway.

Take care! 🙂