How to create a software catalog item for multiple software that are installed with SCCM?

[GayleF]

HI all,

My development team has received a request to combine multiple Software Catalog Items (from one vendor) into a single Software Catalog Item.  Then the user should be able to choose which software to install from a dropdown list (or using a text field). Once the request has been submitted - the software should automatically from SCCM.  

Currently each piece of software has a Software Model, and our Asset Management team creates the software catalog item using a template we created and links the install to our SCCM Installation package.  This creates multiple software catalog items for a single vendor.   What we are looking for is a way to take the 25 items and consolidate into 1 catalog request for that vendor.   

Is there anyway that this can be done without building or scripting an App within ServiceNow?

Here is the actual ask from the user: 

Purpose: Provide a single, general request form where a user enters the Autodesk software title and version; the request is routed to Asset Management to assign licenses and trigger installation via SCCM.

Request title: Autodesk Software Request

Search keywords: Vault; Autodesk; AutoCAD; CAD; Inventor; Fusion

Required fields:

• User name (dropdown)
• Software title and version (open text)

[SAMfluencer786]

Hi @GayleF ,

I would suggest trying this: a single Catalog Item with a Variable Set.

1. Create a single Catalog Item - "Autodesk Software Request" - linked to your existing fulfillment workflow.
2. Add a Variable Set with the following variables: 
   • Requested For → Reference variable pointing to sys_user.
   •  Software Title & Version → Single Line Text (open text, as requested) or a Select Box dropdown populated with your 25 Autodesk titles if you want to constrain choices and reduce Asset Management validation effort
3. Workflow / Flow Designer - your existing SCCM trigger logic can remain largely intact. Route the submitted request to Asset Management via an approval step, then trigger the SCCM installation package using the same mechanism you use today, parameterised by the software title variable value.

If your SCCM packages are mapped 1:1 to Autodesk titles, a short Catalog Script (not a full app) can map the submitted value to the correct SCCM package ID, keeping the workflow generic across all 25 titles.

One quick clarification is your SCCM packages triggered by a fixed package name/ID passed into the workflow, or does the workflow look up the package dynamically via the Software Model record?

If this helped - amazing, you're welcome, go click Helpful and Accept as Solution. If it didn't - well, at least you learned what not to do. Either way, we grow. 

Cheers, Abby

ITAM Principal Solution Architect