As a Preferred Distributor Partner, SHI offers an integration to send asset information such as Model, Manufacturer, Serial Number, Purchase Date, and PO Number directly into Oomnitza when the product is ordered.
This integration is built and hosted by SHI. For further details please see below. For any questions, or to request an integration, please contact your SHI representative and ask about the Oomnitza EDI integration. (Please note that this integration is still in Beta.)
For more information on SHI, visit shi.com.
SHI is able to provide the following fields through their integration. These fields can be configured to meet your business needs.
shi_sales_order_number model device_name notes purchase_price shi_qty_invoiced shi_ship_date shi_ship_name shi_ship_address1 shi_ship_address2 shi_ship_address3 shi_ship_city shi_ship_state shi_ship_postalcode shi_ship_country serial_number barcode shi_asset_type shi_operating_system shi_maintenance_start shi_maintenance_end
To bring these fields into Oomnitza from SHI, corresponding fields must be created in Oomnitza. These fields correspond based on their Oomnitza External IDs. To create these fields, navigate to Customization, select "Add" and Name the field after the described field listed above.
NOTE: Fields can either be entered verbatim from the list above, or entered with spaces (as seen in "Serial Number" below, and the external ID will be generated with the appropriate underscores. Please also note that if an external ID already exists in Oomnitza, subsequently created fields with the same name will be given the id "<external_id>_1" where <external_id> is the name of the field.
You can confirm the field's external ID from the customization field by selecting the the custom field and looking at the External ID section:
For common fields coming from SHI, the IDs above match directly with default fields in Oomnitza. Examples of this include Serial Number, Barcode, Model, and Asset Type. Other fields that may have significant differences have "shi_" added to the beginning. Some of these fields, particularly Manufacturer, may need to be transformed in order to map to the proper field in Oomnitza. This should be achieved using Workflows.
An example of this would be converting SHI Manufacturer values to Oomnitza Manufacturer values:
In the above example, we begin on creation of a New asset, then use Conditional Threshold Blocks to check for the presence of a given manufacturer in the information coming from SHI. For example, here's the Dell conditional Update Block:
And the corresponding Update Block:
These blocks can be chained to support any number of manufacturers.
SHI offers the ability to filter the data sent through the integration. By default, SHI allows 5 separate filters to be applied to the report. One filter per one column/field.
- More can be allowed, but extra development would be required to allow for more than 5 separate filters.
- With each filter, you can have up to 3 separate conditions. Keywords "AND" and "OR" can be used to specify whether they are all required, or only 1 must be met.
(Filter by Purchase Date): Purchase Date Doesn't Contain '10/23/2019' and Doesn't End With '2020'
This example will only use items purchased in any year that is NOT 2020, but will also exclude purchases made on 10/23/2019
Oomnitza Workflows should be used for additional filters beyond the 5 available from SHI, or more advanced filtering. For example, Oomnitza's "Archive" Workflow block can be used to automatically archives unwanted objects, and logic like the workflow shown above can be used to transfer and transform data among fields in Oomnitza.
What SHI needs from you:
To configure the integration in Oomnitza, SHI requires a few key pieces of information to get it set up.
- Oomnitza Endpoint URL (e.g. shi.oomnitza.com)
- Client API token (See Below)
- Filter requirements
Steps below take place after customers work with Oomnitza to create an environment for that customer/company.
Acquiring a Token:
In order to generate an API token in Oomnitza, navigate to the Settings page and select “API”.
From the API page, Select “+ Add New” to generate a new API token. You’ll be prompted to enter a name for the token:
Once you’ve done this, you’ll be given the new API token. This will only be displayed once, and cannot be recovered if lost, so make sure to store it somewhere secure:
For external services, we recommend creating a new User that is specific to that service. Once created, you can log in as that user and generate an API token associated with that account. This makes the activity of the API token easier to identify and control, and prevents issue as your team members change.