Good afternoon,
Some basic assumptions:
- HAM plugins are installed
- Set up an any business rules for Approvals based off company policies.
- Ex: if an item is over $50 - it will need their manager approval or if the item is over $100 it needs their manager and their VP approval
- Set up of the Service Catalog
Let's walk thru the workflow:
Service Catalog (trigger) - this is where the end user would go into the Service Catalog to add a widget to their cart. The items will show up as a requested item in the related lists once the request is submitted. Once the end user selects the items that they need - they would submit the request.
Ask for Approval (action 1) - Based off any business rules on might have to go thru a subflow to get the approvals needed. An example of a business rule is above with the cost of the item driving the approval process.
Waiting for Condition where (Sourced is true) (action 2): The system checks to see if the item needs to be sourced - PO information should be captured. The purchase order process might be in another system that will have to be imported into ServiceNow. If no PO is need - it moves to the action 5.
Waiting for Condition where (Receive is true) (action 3): The request is waiting for the items to be received
Stage Assets (action 4): Assure items are in an inventory lifecycle status (ie. In Stock, Reserved, etc) and ready for deployment.
Create Catalog Task (action 5): Once the items have been received and are in stock - a catalog task is created for each of the requested items. A catalog task will be assigned to a group and/or an individual who will perform the action requested in the catalog task.
Deploy Assets (action 6): The item is deployed to end user for each catalog task - ServiceNow will be updated with any other attributed that you might be tracking. Once you close all the catalog task - this will automate the closure of the parent request.
If my answer helped you in any way, please then mark it as helpful.
Kind regards,
Randy
