General Description of the Feature

This feature enables the possibility for a Salesperson to create a sale process for a vehicle which is located within the AVAG Locator, through Digital Sales Workplace. AVAG Locator is a 3^rd party Application that is developed by AVAG. The Salesperson selects a vehicle from the AVAG Locator and reserves it for a predifined period. This triggers automatically a Web-Request from the AVAG Locator which means that Data is send to a Web Service provided by OD, and through the necessary mapping of the fields that are sent from AVAG Locator with the fields of the OneDealer base, the selected vehicle is displayed in the Vehicle Inventory gridlist of DSW and it is available for the initiation of a sales process (Offer, Test Drive, Order, etc). 

The following columns are enhanced in the Vehicle Gridlist page:

• Third Party Application Code
• Third Party Vehicle Number
• Third Party Vehicle valid until

Checkbox of "Show only third party vehicles" is available in the Advanced Search 

The following fields are enhanced in the Vehicle Card page:

• Third Party Application Code
• Third Party Vehicle ID
• Third Party Vehicle Number
• Third Party Company
• Third Party Location
• Third Party reserved by
• Third Party Vehicle valid until

Basic data logic validations

• Every vehicle that is displayed in the Vehicle Inventory gridlist and comes from the 3^rd party Application of AVAG, will be available in DSW for a sale process, only for the reservation period that was predifined when it was selected from AVAG Locator enviroment.
• If the reservation period is exceeded then the vehicle will not be displayed in the Inventory gridlist.
• If the reservation period is exceeded and a sale process is initiated for this vehicle (i.e Lead is created), then the process cannot be progressed into an Order. The Salesperson has to renew the reservation in the AVAG Locator (if the Vehicle is still available there). 
• The switch of "Show and use third party vehicles" inside "Third Party Application Vehicle Setup" page enables the dislpay of the following entities inside DSW:

1. Vehicle gridlist columns: "Third Party Application Code", "Third Party Vehicle Number", "Third Party Vehicle valid until"
2. Checkbox of "Show only third party vehicles" in the Advanced Search
3. Vehicle Card page fields: "Third Party Application Code", "Third Party Vehicle ID", "Third Party Vehicle Number", "Third Party Company", "Third Party Location", "Third Party reserved by", "Third Party Vehicle valid until"

When this switch is on "Yes" then all the above are visible. When it is on "No" then all the above are not visible.

Business Benefit

This feature enables the possibility to a Salesperson to start a sales process in DSW for vehicles that come from a 3^rd party Application.

Configuration 

• Third Party Application Vehicle Setup Page

Business Case ID 13300 must be applied to the user.

Create Menu Item Instructions:

To create the menu item which will redirect the user to this page, do the following.

First navigate to the Menu Administration page by opening the menu and searching for "Menu" or by clicking "All Apps" → "Setup" → "Administration" → "Menu". Then scroll down to find the "Setup" item.

Click on the "Setup" menu item and then click the "Add New" button.

Click on the "New Item" and fill the values as shown in the figure below.

Then with the newly created item selected, press the "Add New" button again and fill the fields shown in the figure below.

Once you have completed the above click on the save button located on the bottom right of the page.

Values

Third Party Application

Vehicle Setup

Preview

Navigation

To view this page navigate to the menu located to the left side of the navigation bar and click on "All Apps".

Scroll to find the "Setup" menu item and click it.

Click on "Third Party Application".

Click on "Vehicle Setup".

Setup keys and resource keys required for the "Third Party Vehicle Application Setup" page are the following:

• Mapping setup between AVAG Locator and OD

The AVAG Locator Mapper requires a Mapping Relation between OneDealer and AVAG Mapping Systems.

Make sure that the AVAGLocatorMapperApiKey Setup Key is set to the same API Key set in the Mapping Relationship.

Make sure that an AVAG Mapping System is set for the installation you are in.

If not, please follow the steps described here https://wiki.onedealer.com/x/mxLx  and create a new one.

The required OneDealer entities to be set as Mapping Objects are the following:

Additional Information

None