Live Chat

Chrome Data VIN Decoder – Feature

The Chrome Data VIN Decoder feature is used to communicate with the 3rd party Chrome Data service for real-time VIN look-ups in your Ivinex system.

Note: Minimum Required Ivinex Version: 4.0
Note: The Chrome Data VIN Decoder feature is not turned on by default. If you feel you could benefit from the chrome data VIN decoder feature, please contact us, and we will enable it for your Ivinex site.

Feature Setup

Once the feature has been activated you need to follow these initial steps:

  • Open Ivinex Admin
  • Click System Preferences
  • Click Feature Manager
  • Click Settings for the Chrome Data VIN Decoder Feature
    • Put in your Account Number and Account Secret (which you will get from the vendor)
    • Save your settings
Fig. 1 - Initial Setup

Fig. 1 – Initial Setup

Module Setup

After the initial setup, please follow these additional steps

  • Create a module to hold your inventory
    Note: If you have an Inventory/Vehicle module already created in your Ivinex system, then you can skip this step. It is possible to use ANY module with this feature, the name of the module does not matter.
  • In your Inventory/Vehicle module, you need to create the fields where you will store the data returned from the service.  The following data is returned from ChromeData…
    • Year
    • Make
    • Model
    • Style Name
    • Trim
    • Body Type
    • Engine Type
    • Fuel Type
    • Driving Wheels
    • VIN: You must also create a field to store the VIN number as this is what the feature will use to lookup data with.
  • At this point you get to choose how this feature will be triggered.  It is recommended to use one of the following…
    •  When a record is updated (use a filter to only lookup vehicles that have not already been looked up before).
    • When a button is pressed
      • If you choose to use this trigger, you will need to create a button (Field Type) in the Inventory/Vehicle module as well.

Once you have all the fields created in your module, you need to create the workflow that will lookup your vehicle information and store it in your Inventory/Vehicle record.

Workflow Setup

Please follow these steps to create the workflow.

Tutorial: Workflow Wizard
  • Open Ivinex Admin.
  • Click Workflow Wizard.
  • *Optional: Create a new group to hold your VIN lookup workflow actions.
  • Add a new workflow by clicking the ‘Add New’ button.
  • Type a name for this workflow (ie: Lookup VIN in Inventory Module).
  • Select a type (as stated above, either When a record is updated, or When a button is clicked).
  • Select the Inventory/Vehicle module you have just created or modified.
  • Add a new Action by clicking the ‘Add Action’ button.
  • Type in a name for this Action (ie: Get vehicle info).
  • Select ‘Get Vehicle Information’ from the Action dropdown… this will open a form where you are going to map the fields from your Inventory/Vehicle Module to the data that ChromeData returns.
    • You can select as many of the fields to store as you want.
    • When you are done mapping the fields, click save, and then click save.
    • Close the Workflow Wizard main page.

Button Setup

Please follow these steps to assign the workflow to a button.

If you chose to use a button for the VIN lookup, you will need to click on the button in the admin, and select the workflow that the button will trigger.

  • Open Ivinex Admin.
  • Click your Inventory / Vehicle Module.
  • Click on the button that will be used for VIN lookup.
  • Select the workflow that will be used for VIN lookup.
  • Save your changes.
Fig. 2 - Button Triggered Workflow

Fig. 2 – Button Triggered Workflow

How to use

You are now ready to lookup VIN numbers.

  • Open the Inventory/Vehicle module you selected.
  • Create a new record and type in a VIN.
  • Save the record (this will not trigger a lookup).
  • Once the record has been created and saved, you can now click the button you assigned the workflow to or click the Update button which will cause a lookup.
  • Reload the record and all the appropriate data should be stored in the record

Revisions

Tags: , , ,

No comments yet.

Leave a Reply

%d bloggers like this: