Catalog task group assignments as Configurations

JPing
Tera Expert

Hello All, 

 

In my company we have over 90 Catalog items. Each Catalog item corresponds to a specific workflow Designer flow (if not then old school workflow editor). 

 

Over the last 5 years of have SN, the teams have changed - some teams are gone, new teams take over old catalog item fulfillment. 

 

My problem is that in each flow there is at least 1 catalog task that get created (sometime only if automation fails). When teams change, it is difficult to figure out if that team was hard coded into a catalog task as the assignment group, the obvious byproduct is that catalog task are being to teams that at inactive, or have no users in them. 

 

Has anyone figured out and elegant way to manage this? 

 

 I have the ability to write scripts that will scrub flows and find if  inactive group sys_id appears in a flow and send a report. It's an ok solution, but I fell like there should be a better solution. A central table that I can easily link flows to assignment groups, but what if I have a flow that has two or more catalog task creation that go to different teams. 

 

I would be interested in what some developers have thought of to reduce the hardcoding of values in their flows, and moved it to a configuration.

 

Thanks in advance. 

0 REPLIES 0