Update Incident Record - Assignment Group
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Using Workflow Studio to build auto assignment for incidents. I am not able to pass the data pills from the Trigger Record: (Assignment group [Record]), (Assignment group [Sys ID]), or the (Assignment group [Name]), to the Assignment group field of my newly created incident. I am currently doing a Look Up of the specific Assignment group record to ensure I'm getting the right Sys ID, and when passed to the incident that is also not working to populate the Assignment group field.
Trigger conditions are met [New/Updated Record: Conditions: Vulnerable Item with {X risk score} and assigned to {target Assignment group}] =
1. Create Incident Record
- populate with the relevant information from the trigger record
2. Log : info: {Incident Record}
3. Wait 5 seconds
4. LooK Up Group Record
- Group [sys_user_group]
- condition Sys ID: is: {data pill for Assignment Group from trigger record}
5. Update Incident Record
- Target created incident record
- Assignment group: {data pill from Look Up Sys ID (GUID)}
6. Log: info: {Incident Assignment group}
The flow completes with no errors, but it never assigns the Assignment group.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
- In your Create Record or Update Record action for the Incident, map the Assignment group field using the output record pill from your lookup
- Ensure the Look Up Record action searches the sys_user_group table using a correct condition
- Drag and drop the complete Group Record data pill directly into the assignment group field of the incident
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Is the Vulnerable Item table a custom table/scope? It sounds like you may need to enable some cross-scope privileges to that scope to interact with the global scope.