Navigating to an approval on a REQ from the task table for a report
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi All,
I am trying to create a report on the task table. It is a dynamic that shows the user a list view of everything assigned to them. They created a new process for one of our requests and for some reason the approval is populating on the REQ instead of the RITM. Trying to figure out how to add the approval "state" field to the report. By approval I mean, requested, not yet requested, approved. Normally I see these approvals only on the RITM.
Couple things, our SNOW instance is a mess because they tried for 4 years to outsource it's support to folks who didn't know what they are doing, and I am completely new at this.... long story, but if there is anything I'm saying that doesn't make sense it is fair to assume I don't know what I am talking about LOL
Thanks for any help!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Here is the report and the columns I have selected, and it is pulling from the Task [task] table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
I had a similar request from leadership at my company. They wanted me to create a Divisional Dashboard that allowed the Regional Support Team to view all RITMs based on the Approval state (All, Not Yet Requested, Requested, Approved, Rejected, Cancelled, No Longer Required, More Information Required, and Duplicate).
I had to create a Database View with the sc_req_item and sysapproval_approver tables. Like this:
And this is what the Regional Support Team can see on the dashboard.
I hope this helps 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
forgot to post the picture of what the Regional Support Team can see now. I hope your team can fix the REQ on the RITM (most likely a workflow that is being picked up on the REQ or they selected the incorrect table name when setting up the action).
