Configuration guide: Device assignment verification
Introduction
If the ServiceNow Hardware Asset Management database isn’t kept current, it can lead to a range of operational challenges. Inaccurate documentation of a device’s current user can disrupt resource retrieval processes, causing delays and confusion when devices need to be collected for maintenance or upgrades. This discrepancy can also result in applications being installed incorrectly or not at all. Thus, maintaining up-to-date assignee information is crucial for the efficiency of resource retrieval and the security of the overall IT asset management system.
This page will guide you through the structure of the content.
Content list and dependency
| Type | Name | Description | Dependencies |
|---|---|---|---|
Device assignment verification | Verification and update of device assignee information. | ||
Device assignment verification - Workflow invoke | Ask if user is primary owner of the device. | Workflow parameter activates this campaign. |
Configuration guide
To effectively use this library pack, the content must be installed and configured appropriately. Below are some suggested steps to install and configure the content properly before use.
Step 1) Install library pack content
Go to the Nexthink Library and install all required content.
Step 2) Edit campaigns
Navigate to the manage campaigns administration page to review and edit your campaigns.
For each installed campaign, please ensure to:
Customize the sender name and image.
Review and adjust questions.
Publish the campaign when you are ready to use it.
We recommend the following configurations for these campaigns:
| Name | Trigger | Priority |
|---|---|---|
Device assignment verification | API | Urgent |
Step 3) Configure ServiceNow integration
The configuration of connector credentials is essential for enabling API calls. See detailed information at https://nexthink.gitbook.io/opd/integrations/outbound-connectors/connector-credentials. Each Service/API thinklet has a dropdown field for credentials that needs to be filled out. When the workflow is installed or copied from the Library, this field will be blank as it is a local setup of each environment and is not included in the Library.
Step 4) Check workflow parameters
The parameters for the workflow are provided below. There is no need for adjustments as the preset values are already optimized for use.
Ask for permission?: This parameter controls the option of updating the assignee with or without user consent. It has two possible values: "Yes", which means that a campaign should be triggered to obtain user consent, or "No", which means that the changes of device assignment will be done without user consent.
Event trigger AD user name: This parameter is essential for the workflow’s integration with the event trigger. In the subsequent “Maintain workflow trigger” step, this parameter will be associated with the user AD name field in the event trigger’s NQL query.
Event trigger device name: This parameter is essential for the workflow’s integration with the event trigger. In the subsequent “Maintain workflow trigger” step, this parameter will be associated with the device name field in the event trigger’s NQL query.
Step 5) Maintain API thinklets locally defined credentials
Each Service/API thinklet requires locally maintained credentials. In this step review all relevant thinklets and maintain credentials.
Step 6) Maintain workflow trigger
This workflow is designed to run automatically using an event trigger.
The following query can be used to trigger a workflow event. It selects all non-virtual devices. If necessary, manual custom fields can be included in the query to exclude specific devices, such as “kiosk” or “training” devices, or to exclude service desk agent users who frequently log in to other users’ devices.
Usage guide
Your content is now configured and ready to be used. For usage overview and recommendations, you can visit the usage guide:
Usage guide: Device assignment verification
RELATED TOPICS
Last updated
