Source Request Configuration Question (AKA Procurement Plugin)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-06-2023 12:13 PM
The procurement plugin uses the Source Request workflow to generate a single procurement task to source ALL software items on a request.
Has anyone configured the Source Request feature to generate separate Source Requests to different groups based on the software requested?
Currently all our software requests go to one one group to complete the allocation. We are asked to have Survey Monkey requests go to a different group.
I was able to update the Source Request workflow to generate separate catalog tasks but each task opens the same Source Request.
For example a catalog task is generated on the REQ to Group A for a Survey Monkey request and a separate catalog task is generated on the REQ to Group B for any other title (Task.jpg).
The trouble is that each task displays both software items to allocate (Source Request.jpg).
Is it possible to generate separate Source Requests on the same REQ?
Ex. The task to Group A would only display the Survey Monkey Source Request to allocate and the other task would display any other software titles except for Survey Monkey?
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-08-2023 11:13 AM
@mrcorbeaux I don't think it's possible to generate separate source request tasks. On your example, does the other group maintain the software entitlements for Survey Monkey (e.g. if running low, would they initiate the additional purchase or do they maintain a number of licenses and review usage regularly)? If they don't do that at all then might as well remove the sourcing task for that specific software and automatically generate the task under the RITM itself so they can handle the request? If they do handle it, it would mean that there are multiple groups handling/updating your software model & entitlements. This would be tricky because I don't think there is a way to separate the source request tasks on the same REQ.
Hope this helps! Please mark the answer as correct and/or helpful based on impact.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-11-2023 02:00 PM
Multiple groups are involved. The two groups mentioned would just be doing the sourcing task/allocation. We have a third group that purchases the bank of licenses. Are you saying its possible to have the Source Task generated under the RITM and not the REQ?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-18-2023 10:16 AM
Unfortunately, the Source Request page isn't open to modification.