Generic workflows for service items

Handling custom fields are a paint in the A***. I hope the new global field function going to solve the issue. 

The best solution I come to is to do a API request to the service item for the ticket using the webrequest node. This works only if there are one item( I hope looping will solve having more then one). 

In my parser node I add all custom fields for all service items. Best if most of the fields have the same name. Like First name Last name etc. The parser do not need to match the webrequest. If the data isn’t in the payload that the parser are looking for you will only get a empty 

Use custom objects for drop downs if you can. Then you can use the output from the parser to read the custom object(Record ID) 

Use expression(node) and in conditions to get more generic flow as well. 

You can use custom objects and reader nodes within the Workflow Automator. Start by creating a custom object that maps service items to their corresponding teams, including fields like 'Service Item' and 'Assigned Team.' Once the custom object is set up, populate it with records that specify each service item and its associated team.

Next, configure the Workflow Automator to trigger when a service request is raised. Use a reader node to fetch data from the custom object, ensuring that the 'Service Item' field in the custom object matches the service item in the request. If a valid record is found, a conditional node should verify the match. Finally, an action node will use the data from the reader node to assign the request to the correct team.