B.1.2- Integration between OneDealer DSW and INCADEA idms

Introduction

The standard internal APIs have been implemented for the interaction between DSW and iDMS, however the swaggers used to call iDMS are different from the standard ones. 

Prerequisites to establish a successful interaction 

• General configuration (please refer to this page: Configuration required to establish the communication between DSW and ODIL
• Upload Vehicle model tree (please refer to this page: Model tree
• Object types mapping (DSW ↔ iDMS) (please refer to his page: Object Types Mapping

Business Processes Covered in this Page Tree

• Business Partner (Create and Update). Please refer to this page: Business Partner Create and Update
• Publish Vehicle. Please refer to this page: Publish Vehicle
• DMS Lead Qualify Process. Please refer to this page: Lead Qualification
  • VOI from Stock search. Please refer to this page: Stock Search
  • VOI from Inventory Vehicles. Please refer to this page: Inventory Vehicles (New/Used)
• Retail Sales Offer 
  • Vehicle Reservation
    • Inventory Vehicle. Please refer to this page: Reservation Functionality for known VINs
    • Stock Locator. Please refer to this page: Reservation as WF Activity
  • Trade-In. Please refer to this page: Trade-in
  • Test Drive. Please refer to this page: Test Drive
• Retail Sales Order. Please refer to the page: Retail Sales Order
• Wholesales Offer. Please refer to the page: Wholesales Offer
• Wholesales Order. Please refer to the page: Wholesales Order
  • Assign VINs to a wholesales order. Please refer to the page: Assign VINs
• Lead status Update in iDMS
• Order status update in DSW

This product line is based on the decoupled product Sales and Lead (DSW) and it covers the integration end-points listed in this page: Integration End-Points