- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2022 09:21 AM
We have an IT Adhoc catalog item
Part of that request includes the user putting in a project title. We want to use that project title for a few things. Here is what I am have done and am trying to do
- User enters a project title
- Flow takes that project title and in the catalog task uses it for the short description
- It also takes that project title and makes it the short description of the RITM
This is great, BUT
I need it to also use it to update the REQ with the title as the short description
Example
I created a request
SCTASK - Short Description is the project title
The RITM shows it to
but the REQ table doesn't
Is it possible to update using Flow?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2022 10:06 AM
Yes, you are almost there, you need to do an additional dot-walk step as shown below
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2022 09:49 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2022 10:06 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2022 10:26 AM
AMAZING!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-05-2024 08:02 AM
Why the heck should we have to build this as admins? Why isn't this just an out of the box thing that REQ has a short description and description based on what was requested? What a frikin' weird thing to skip over especially since out of the box they added the details to the email notifications... why the heck isn't this done by default? Someone give me a historical or professional reason to leave the short description and description blank at the REQ level? huh? WHY!!!!???!!!????
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-05-2024 08:33 AM
I am not a SN employee, so this is in no way an official statement.
The REQ layer is our shopping cart, we can have multiple items (RITMs) in our cart.
Since we can have multiple RITMs, even from totally different Catalog Items under a single REQ, it becomes hard to decide on a "generic, on fits all" short description for this layer, so they simply decided to leave it empty and left this task for us to do.