- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2024 12:21 AM
Hi,
I have a two requirements.
1--> To create request through inbound action using a particular catalog item.
2--> To create another task simultaneously within the same RITM with different assignment group.
I am able to complete the first requirement however unable to achieve the second one.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2024 12:34 AM
Hi @Puneet4418,
You can define a workflow/flow for your catalog item which would create a task.
There is no need to create a task within the inbound action, once your request is created, it will follow the workflow/flow associated with the catalog item.
By doing this, you are also ensuring your request is following a standardized process.
Cheers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2024 02:01 AM
Hi @Puneet4418
Inbound action is just a trigger point which create a record in tabel. Once record get created , you can attach the Flow which will create the task for you.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2024 12:34 AM
Hi @Puneet4418,
You can define a workflow/flow for your catalog item which would create a task.
There is no need to create a task within the inbound action, once your request is created, it will follow the workflow/flow associated with the catalog item.
By doing this, you are also ensuring your request is following a standardized process.
Cheers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-03-2024 06:29 AM
Hi @James Chun,
Thanks for the suggestion. Updating the WF resolved my issue.
I have one more query:
in the email body we have an email address and I want to populate that user in the "requested_for" variable of the catalog item.
Email body has a fixed format. i.e.
Email Address:
Country:
City:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-03-2024 11:48 AM
Hi @Puneet4418,
To parse the inbound email, you can use the 'email' object.
Have a look at the example below:
I believe this applies to both Inbound Email Flow and Inbound Action.
Cheers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2024 02:01 AM
Hi @Puneet4418
Inbound action is just a trigger point which create a record in tabel. Once record get created , you can attach the Flow which will create the task for you.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************