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

[MattSN]

I came across this thread while also looking to manage approvals with a lookup. It is slightly more effort to implement, but long term Decision Tables are the way go. Have look at Change Management Approvals in the Utah release. They are using DT's and maintaining the approvals is both powerful and easy to manage for anyone.

[SumanthDosapati]

Hi,

Instead of hardcoding, You can use system properties to store the sysid of groups and call the property in approval 

> Create system properties for each group which stores the sysid

> Use the system property in workflow to trigger approval as below

gs.getProperty('property name');

Mark as correct and helpful if it solved your query.

Regards,

Sumanth

[SwarnadeepNandy]

No, I don't think, it is great place to store matric of configuration data. Our plan is to create a table, but were looking for any OOTB approach by ServiceNow.

Thanks,

Swarnadeep Nandy