The XENTRY Portal pro interface supports dealers with the diagnosis process for a vehicle in delivering information about the required labour, parts and service (measure) packages. XENTRY portal provides several possibilities to gather relevant labour, part and service packages for the vehicle assigned to a job via the EWA net interfaces (such as WIS/ASRA and EPC) and service measures via interfaces with EVA.
The XENTRY Portal pro interface in Autoline was created to provide an integrated solution for the communication between the Autoline and XENTRY Portal (version 1.4.5) via the data server. The following communication scenarios used:
Synchronous requests initiated by Autoline
Requests initiated in Autoline requiring a direct response (receipt confirmations) from XENTRY Portal.
Synchronous requests initiated by XENTRY Portal
Requests initiated in XENTRY Portal requiring a direct response from Autoline.
Each communication between Autoline and XENTRY Portal contains:
Business context: Provides the XENTRY Portal Pro version, the recipient DMS and which operation & type (service message) is required.
User context: Provides information about the user starting the communication. User ID of XENTRY Portal, User ID of Autoline and preferred language of the user.
Process context: Provides the date and time the communication is started and the Job ID allocated by the InitJob process during export which is used to allocate the Autoline WiP number during import.
Service Message: The actual request or response operation with the information required for the transfer.
The actual request or response operation with the information required for the transfer. Below the process steps of the communication are displayed:
| Process Steps | Main - Service Message | Description |
|---|---|---|
| 1. | InitJobRequest | Request by Autoline
Starts a new job in XENTRY Portal linking it to a specific Autoline WiP for a specific Point-of-sale company. Upon sending the request the Autoline WiP is locked preventing the users from using the WiP. The Autoline WiP is unlocked, when the request was not successful as XENTRY Portal because was not able to take control of the job. Depending on the error situation the request can be attempted at a later moment in time or the WiP is recalled to proceed in Autoline without the XENTRY Portal functionality. |
| 2. | InitJobResponse | Response by XENTRY Portal
When an InitJobResponse is received from XENTRY Portal the WiP remains locked in Autoline until control is transferred back via a TransferJobToDmsRequest, initiated in XENTRY Portal. |
| 3. | TransferJobToDmsRequest | Request by XENTRY Portal
The TransferJobToDmsRequest is sent from XENTRY Portal to Autoline to give control of a job back to Autoline together with the new/changed data XENTRY Portal has about the job. |
| 4. | TransferJobToDmsResponse | Response by Autoline
When a TransferJobToDmsRequest is successful a TransferJobToDmsResponse is sent so that the Autoline WiP is unlocked when the user processes the information received from XENTRY Portal. The WiP in Autoline will remain locked as XENTRY Portal stays in control of the job, when the request was not successful. |
| 5. | TransferJobToAsmRequest (optional) | Request by Autoline
Note: WiP in Autoline locked until job is transferred back to Autoline When a job was initiated from Autoline, sent back from XENTRY Portal and the user wants to perform additional actions to the job in the XENTRY Portal portal a TransferJobToAsmRequest is sent by clicking the XENTRY Portal button in Point-of-sale. Autoline automatically recognizes the job being linked to XENTRY Portal by the XENTRY Portal job ID stored on the MB extended header and will not initiate a new job in XENTRY Portal but send over the WiP data linked to the XENTRY Portal job ID. |
| 6. | TransferJobToAsmResponse (only sent after TransferJobToAsmRequest) | Response by XENTRY Portal
When a TransferJobToAsmRequest is successful a TransferJobToAsmResponse is sent. |
| 7. | FinishOrderRequest | Request by Autoline
When an Autoline WiP is linked to an XENTRY Portal job and is fully invoiced a FinishOrderRequest is sent to XENTRY Portal to close the job in the portal as well. |
| 8. | FinishOrderResponse | Response by XENTRY Portal
When a FinishOrderRequest is successful a FinishOrderResponse is sent. |
| Process Steps | Supporting - Service Message | Description |
| 1. | GetDmsSettingsRequest | Request by XENTRY Portal
The GetDmsSettingsRequest triggers the function in Autoline to retrieve the invoice codes used in Autoline point-of-sales. The invoice codes from the first point-of-sale company found are sent back, hence it is obligated to have the same for all Point-of-sale companies using the XENTRY Portal. Note: It is possible to have a different set of invoice codes per Autoline point-of-sales company, in case a valid Outlet GSSD id is sent via the request of XENTRY Portal and the interface to XENTRY Portal pro (Branch 4) function is used in Autoline while having a Outlet GSSD id setup in the XENTRY Portal Pro parameters. |
| 2. | GetDmsSettingsResponse | Response by Autoline
When a GetDmsSettingsRequest is successfully received from XENTRY Portal a GetDmsSettingsResponse is generated. The response contains the warranty payment types/codes, description including the (extended) suffix (sequence number). |
| 1. | RunVerificationRequest | Request by XENTRY Portal |
| 2. | RunVerificationResponse | Response by Autoline
When a RunVerificationRequest is successfully received from XENTRY Portal a RunVerificationResponse is generated. |
| 1. | GetPricesRequest | Request by XENTRY Portal
The GetPricesRequest is received by Autoline from XENTRY Portal. The WiP number required is taken and the Parts, WorkItems, ServicePackage price request is performed. So prices collected are related to the customer attached to the WiP and will follow the same rules as the price calculation used when manually adding the lines to the loaded WiP in Point-of-sales. Note: The GetPricesRequest does not actually add any lines to the WiP loaded. |
| 2. | GetPricesResponse | Response by Autoline
When a GetPricesRequest is successfully received from XENTRY Portal and the prices are collected from Autoline a GetPricesResponse is generated |