Table of Contents

Status

DONE 

Author

Feature No.

ABES-51 - Getting issue details... STATUS

Test Case No.

QA-5731 - Getting issue details... STATUS

Related Features2.68.7 - "CreateInquiryInterestByCase" API - Auto Qualification
Tenant

Product (Demonstration)

Main Version

3.18.0

Patched Versions

3.16.8

Conf. for Technical Upgrade

Yes

General Description of the Feature

This feature introduces various enhancements to the inquiry service within the DSW platform, facilitating seamless creation of Opportunities and vehicle reservations directly through the "CreateInquiryInterestByCase" API. Customers can now leverage an extended set of functionalities to streamline their transactional processes. Key components of this upgrade include advanced auto-qualification mechanisms, trusted source logic, and comprehensive API integration.

Business Partner Auto-Qualification

A significant advancement is the refinement of the business partner auto-qualification process. Upon inquiry creation, an auto-qualification process occurs if the auto qualification flag is set to True and no business partner (BP) is assigned.

  • Previously, only a duplicate check was performed, resulting in no change if no exact match of a BP was found.
  • Now, if no BP or multiple matches are found, a BP (and a CP) is created, GDPR notification consents are added if provided, and a "BillTo" address is created if necessary. The inquiry qualification status is then updated accordingly.

Currently, the duplication check logic prioritizes company matches. If no company matches are found, the system proceeds to search for private matches. If a private business partner is found during this process, it constitutes a match.

For Company Business Partner types, the matching criterion is the "Company Name" field, whereas for Private Business Partner types, it involves matching the "First Name," "Last Name," and any of the phone numbers.

double exclamation mark It's crucial to note that if a business partner is found and matched during the automatic duplication check, the inquiry, opportunity, and reservation are associated with this existing business partner, and no updates are made to its existing data, even if it differs from the data provided in the request. However, if no exact match is found or multiple matches are found, a new business partner is created from scratch, incorporating the data provided in the request.

Trusted Source Logic

A crucial element of this feature is the implementation of "Trusted Source" logic within the Key Relation configuration. This enhancement ensures data integrity by designating certain key relation records as "trusted."

Under this classification, specific operational logic is invoked during the inquiry creation process. Notably, for designated case types such as "Vehicle Sales" (case type: 200) and "Stock Vehicle" (case type: 6) the system automatically creates reservations based on predefined parameters, thereby streamlining transactional workflows.

Reservation

Within the request body of the API a new set of properties have been added, controlling the type, duration and reason of the Reservation. 

On the response of the request, it is always mentioned if the reservation for the provided vehicle was successful or not.

Reservation properties- Request
"Reservation": {
	"Duration": 48, // in hours
    "Type": 2, // Possible values: 0 - Test Drive, 1 - Transport, 2 - Sales, 3 - Service, 4 - Courtesy, 5 - Motorcycle Test Ride
    "Reason": "Sales reservation for online Sales - publication 5847" // Free text
}

Please note that if a vehicle currently has an active reservation of type "Sales," it cannot be scheduled for any additional sales reservations, irrespective of the date-time or associated business partner. However, for all other reservation types, a vehicle can accommodate multiple reservations, whether overlapping or not, and with various related business partners.

Cases that a reservation might be unsuccessful:

  1. the respective Inbound Key is not marked as Trusted
  2. the request doesn't include full information about the reservation: Duration, Type, Reason
  3. the requested vehicle already has another Reservation of Type=Sales

Inquiry Service API Integration

To leverage the extended functionalities offered by this feature, customers can initiate API calls to create Opportunities and reserve vehicles within the DSW platform. A comprehensive set of parameters must be provided, including essential details such as vehicle identification number (VIN), external system inquiry URL and ID, financial information including down payment details, comprehensive customer information, case type designation, inbound key for system reference, address particulars, and reservation specifics. Upon successful execution of the API call, a notification is promptly dispatched to the designated Opportunity assignee, facilitating seamless integration into subsequent sales processes.

Example of an API request for Case Type 200

/Files/Services/ODInquiryServices.onesrv?m=CreateInquiryInterestByCase
{
    "inquiry": {
        "Interest": {
            "VIN": "WBA71AB0805U32625",
            "ExternalSystemInquiryURL": "https://car1.softly.gr/vehicles/5847",
            "ExternalSystemInquiryID": "5847",
            "FinancialInformation": {
                "FinancingType": "Down Payment",
                "FinancingCompany": null,
                "Duration": null,
                "DownPaymentPercentage": 1,
                "DownPaymentAmount": 225,
                "MonthlyInstallmentPercentage": null,
                "MonthlyInstallmentAmount": null,
                "RemainingValuePercentage": null,
                "RemainingValueAmount": null,
                "FeeAmount": null,
                "Currency": "EUR"
            }
        },
        "CompanyName": "Reiner S.A.",
        "FirstName": "Luca",
        "LastName": "Reiner",
        "Email": "Luca.Reiner@mailinator.com",
        "Phone1": "+4917863258556",
        "Phone2": "+4969045687777",
        "MobilePhone": "+30452369999",
        "Language": "English",
        "CaseType": 200,
        "CampaignId": null,
        "ReferralCampaignHash": null,
        "PreferredUserId": null,
        "InboundKey": "Online_Sales",
        "Street": "Leoforos Kifisias",
        "StreetNo": "44",
        "ZipCode": "15125",
        "City": "Marousi",
        "CountryCode": "GR",
        "Block": "B",
        "BuildingFloorRoom": "3",
        "State": null,
        "PlaceType": 3,
        "Notes": "TEST ABES-51 - 0002",
        "ContactDataPrivacy": {
            "AllowContactBySMS": true,
            "AllowContactByPhone": false,
            "AllowContactByEmail": true,
            "AllowContactByPost": false
        },
        "Reservation": {
            "Duration": 48, // in hours
            "Type": 2, // Possible values: 0 - Test Drive, 1 - Transport, 2 - Sales, 3 - Service, 4 - Courtesy, 5 - Motorcycle Test Ride
            "Reason": "Sales reservation for online Sales - publication 5847" // Free text
        }
    }
}

Process flow


Business Benefit 

This feature streamlines the process of creating Opportunities and reserving vehicles directly within the DSW platform, offering customers a convenient and efficient way to initiate transactions and provide essential information, such as down payment details.


Configuration 

Key Relation

  1. Inquiry Inbound Key: Provide the Inquiry Inbound Key to the service caller and add it to the request object's "InboundKey" field.
  2. Trusted Source flag setup: Configure the "Trusted Source" flag in the Key Relation configuration. Set it to "1" to enable reservation creation based on provided data.
  3. Auto-Qualification flag setup: Configure the "Auto Qualification" flag in the Key Relation configuration. Set it to "1" to enable the automatic BP qualification and automatic Opportunity creation.

Dealer Unit

Ensure there is a record in the Dealer Unit for the "Vehicle Sales" case type assigned to a specific salesperson. This can be done in the Dealer Unit setup page. The assignee can be: 

  • either one for the whole Company or
  • multiple assignees, one per Branch.

If the second case is selected, the request coming from the API should include the targeted Branch Code each time.

Workflow Selection

Ensure that there is a matrix selection of a Workflow for the "Vehicle Sales" case type for all the Makes.


Additional Information

Revised DB Tables & Views

@IDMS_INQKEYRELAT

Column

Description

DataType (size)

U_IDMS_TrustedSource

Indicates that the key relation record is marked as “trusted” from a data integrity point of view meaning that we trust the external system will always provide proper data that can be used to perform a specific logic under this flag.

In our case, the extra logic that was added is the creation of the reservation only for the case types “VehiclesSales” and “StockVehicle” (200 and 6 respectively)

INTEGER NOT NULL

IDMS_INQKEYRELATIONVIEW

Column

Description

DataType (size)

TrustedSource

Links to @IDMS_INQKEYRELAT.U_IDMS_TrustedSource

INTEGER NOT NULL

IDMS_MAINCNTCTPRSNVIEW

Column

Description

DataType (size)

CardName

Linked to OCRD.CardName

NVARCHAR(100)


Write a comment…