See also:
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.
This form is displayed when you click Manufacturer systems (Module) and MB. Mercedes-Benz (Company) > Menu - Utilities > Mercedes-Benz parameters and you browse to Service > XENTRY Portal pro parameters > [no. Company name] on the Project parameters browser. It defines the settings for XENTRY Portal pro in Point-of-Sales.
XENTRY Portal pro active: Select to activate the XENTRY Portal pro function.
Export customer data: Select to include the customer information (Customer element) in the service messages concerned to XENTRY Portal.
Export prices: Select to make the service message GetPricesRequests available for processing and to include the pricing information (within the Part, WorkItem or ServicePackage / ServiceMeasurePackage elements) for the service messages concerned to XENTRY Portal.
XENTRY Portal client url: Enter the URL to display the job in XENTRY Portal in a web browser. This URL is depending on the XENTRY system you use and should be given by the XENTRY team.
Note: Please check if the URL contains the following information: https://***/wps/mypoc?uri=retacc:ASM-Open-Job=%s. Autoline will replace the %s with the XENTRY Portal pro job number.
Recommended service package type: Enter the (fixed)price code, as defined in menu pricing, which is used for loading a package onto the WiP.
Priority required to unlock a WiP: Select the minimum priority to unlock a WiP, which is controlled by XENTRY Portal.
Warning: Please be aware that only a limited number of people should use this unlock function, for example, System administrators with priority 8.
Automatically accept WiP updates: Select to validate the status of the WiP lines in a job received from XENTRY Portal and to automatically accept the update of existing WiP lines or the creation of new WiP lines.
User ID for processing online requests: Enter the user id who can process online request requiring data from Point-of-sale, for example, GetPricesRequests. XENTRY Portal can send requests to Autoline requiring immediate processing and sending the response which are referred to as: Online requests or Synchronous requests. These requests are processed via the Persistent line handler and the XENTRY Portal pro function.
Note: The user requires access to the Point-of-sale company and an operator assigned to the user record.
StarConnect Data Server:
External system ID: Displays the GSSN dealer number of the main outlet of the dealer (retailer) used for the communication between Autoline and XENTRY Portal pro via the StarConnect Data Server.
Two communication types are required for XENTRY Portal pro in the StarConnect data server, which become available via the Add Default Communication Types form.
The External system ID is set up via the StarConnect Data Server - [External System ID] parameters. The first time you can select an External system ID here, Autoline creates a mapping between the current Point-of-sale company and the External system ID in the StarConnect Data Server - [External System ID <-> Company Mapping] parameters. After that you can change the mapping via the StarConnect Data Server - [External System ID <-> Company Mapping] parameters. At least one link between the External system ID and a Point-of-sale company is required in the StarConnect Data Server parameters for XENTRY Portal pro.
Warning: When the mapping between an External system ID and Point-of-sale company is changed, it effects all other interfaces using the same mapping.
Upon saving the XENTRY Portal Pro parameters the Xml Schema Definition (XSD) files are, when necessary, automatically stored in the Transfer base directory which is setup in the General Parameters.
Note: The Transfer base directory should include an absolute path, relative path names (starting with ./ or ../) will cause XSD validation errors when exchanging data with XENTRY Portal pro.
To display the information about XSD's, for example the installed version numbers, select the XML schema tab of the StarConnect data server parameters for the External System ID.
System suffix: Enter the suffix ID for communication with external systems. The suffix is used by XENTRY Portal to make the connection available to the different versions of the backend system.
Outlet GSSN ID: Enter the outlet GSSN dealer code to support the data server in delivering requests, initiated by Autoline, to the correct XENTRY Portal instance for the workshop. Only applicable, when multiple Point-of-sale companies are used with the same External System ID and each Point-of-sale company having their own outlet ID assigned. This effects the following service messages between Autoline and XENTRY Portal pro:
- InitJobRequest
- TransferJobToAsmRequest
- FinishOrderRequest
- GetDmsSettingsRequest
The Outlet GSSN ID is provided in the communication, initiated from Autoline, to XENTRY Portal pro in the above synchronous requests and populated in the GSSN ID field of the Synchronous queue details. This GSSN ID value is not used in case the Outlet GSSN ID parameter is left empty in Autoline.