Service Items Fields

@badettecruise,

I would suggest you create one service item with 

• Employee ID
• Location
• Department 

alone and keep it in draft so that the end users don’t see it, and keep cloning it to make your new service item so that you have it by default.

Cheers
J

 

HI @Jayesh urath

Thanks for your insight! My apologies for not explaining it clearly. My goal is to create Action Blocks in the workflow automator so that whatever the users input in these 3 fields in the service item, it will automatically pick up those information in the agent’s fields. 

I want this automator to be applied on all service items. Unfortunately, 1 field = 1 placeholder ID, which means that I have to do it on ALL service items. 

Hello @badettecruise could you show us an example? I am struggling to understand the use case. If the goal is to have workflow action blocks do specific things to the Service Request based on the contents of those fields, you should be able to trigger the workflow on “Service Request is raised” and then use conditionals to check if box1 is filled in, if box2 is filled in, and/or box3 is filled in. Then branch off from there. @Jayesh urath idea of keeping a “Template” in draft status to clone from is the easiest way of replicating custom fields that you want across all your Service Requests. Hope that helps, let us know if we are misunderstanding your usecase. Take care!