AssetTrack for ServiceNow Architecture

AssetTrack for ServiceNow is hosted from within the ServiceNow instance. It's deployed by installing the application from the ServiceNow app store. All interaction from the client UI is done through the scripted rest api.

The AssetTrack client uses two processors on ServiceNow:

  • The AmiFileServiceProcessor provides the client files for the client. The client can run on any modern browser and our mobile applications.
  • The AmiApiProcessor provides the json service calls for interacting with hardware asset data.

Retrieving Data from ServiceNow

AssetTrack queries ServiceNow for data while users are collecting asset information. For example, AssetTrack users lookup asset records by asset tag or serial number, and then browse the location and user tables to assign those assets to new locations and users. Also, AssetTrack queries the model table when creating new assets to assign ServiceNow models.

All queries are performed through a scripted end point within the AssetTrack Scoped App which then uses the ServiceNow Table API to return relevant data.

AssetTrack_Retrieving_Data_from_ServiceNow.png

Writing Asset Data to ServiceNow

The AssetTrack client sends updated asset information to the TaskSave() scripted rest endpoint, which populates the x_amiam_assettrack_ami_hardware_import_set import set table which then updates the alm_hardware table. This method for updating ServiceNow data is the method approved by ServiceNow for all scoped applications and integrations. It ensures all updates are logged in a standard way for audit and rollback purposes. Any trained ServiceNow administrator is very familiar with import sets and transform maps and can easily control AssetTrack updates to ServiceNow data.

AssetTrack_Writing_Data_to_ServiceNow.png

Have more questions? Submit a request

Comments

Please sign in to leave a comment.