How to create a software requested items??

KM SN
Tera Expert

I have number of software listed in spreadsheet and need to create a request items for requesting software.

now the question hunting me is do we need to create requested item for each software? or can we go ahead with one request item?

the request process thinking to handle either by using virtual agent or by scout? 

I have no clue to go further may i get any inputs on same?

2 REPLIES 2

Mark Manders
Mega Patron

It depends on how your requests are handled. If every piece of software needs different information to be granted or if it needs a different way of handling (approval yes/no, other kinds of tasks, etc), you may need several. If it's all just handled in the same way, you can just use a (multiple) choice variable that contains all software items and create one flow to assign and resolve them all (automatically if needed). 
You can use any kind of handling, but before you start, make sure you have your process so you are not changing it half way through. I would just create the catalog item and wouldn't bother with VA (or at least not more than just a link to the item). Just use the OOB service request functionality.


Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

ericward
Mega Guru

Hey @KM SN , Mark offered some great insight. To further what he said it really depends on if each software has unique info that needs gathered or if everything will be handled close to the same. The approach I take most often is to create a singular catalog item for software request. Within this item you can have a single choice or list collector that looks at the software model table and filters down to certified=true. What this then allows is for your software team to create software models as needed and then certify them so that the list in the catalog item is always up to date. You can also take it a step further and add some custom fields to the model form that are required when certified is marked as true. These can be fields for a variety of use cases but a few examples are to indicate if it is a free or commercial software, or even an ownership group for approvals. That way in your flow depending on which software is selected you can go different paths and/or get different approvals.