CESAR is applicable only to franchises defined in the parameters, all other franchises continuing to function as normal in Showroom. The availability of CESAR also depends on a parameter that controls whether it should be available or not. Any change to that flag is effective for the next attempted connection to CESAR in the quote cycle.
When you carry out an action in CESAR that affects Autoline (such that the processes is identified in the URL details file MS.MB.csurl), CESAR sends back a response. In some instances it may not be successful in carrying out the requested action and it may send back a message informing you that the process has ended.
If the parameter to force customer details is set, customer details must be selected before the connection to CESAR becomes available, otherwise Showroom can connect to it without first selecting customer details.
Note: During installation of CESAR, where there are vehicle records already in the Autoline vehicle stock books module, it is possible to sell that stock using the Autoline Showroom process. However, the CESAR stock availability check (described in the note in the Showroom Enquiries - Select a Model form stage of the CESAR New Vehicle Quotation Process) is not carried out because there is no record of that stock in the CESAR configuration details.
These notes are for guidance only, to enable the Autoline side to function.
Install and configure the stunnel software at the dealership on their server. (See the appendix in the CESAR technical documentation for installation notes).
Start the stunnel software.
Ensure Microsoft Internet Explorer version 5.50 or above is installed on the client PCs.
For Autoline 8.30.9304 it is necessary to define option types that are considered to be factory options (those added to a vehicle configuration in CESAR). These are defined within the Franchise Data / System Maintenance / System parameters. These are maintained at Kerridge access priority 9 and should not normally be changed (8.30.9090 and above).
Ensure the correct sequencing of option types within Franchise data / System Maintenance / Option types. These are maintained at Kerridge priority 9 and shouldn't normally be changed, however in instances where for example packs may be defined as factory options, it may be more beneficial to group the factory options together for navigation purposes.
Setup and define the CESAR parameters.
Setup and define the CESAR user map.
Import the MDPLUS franchise data - there is separate documentation about this specific process.
In the franchise data build specification, create all other non factory option types, for example, dealer options, warranties within franchise data.
In the franchise data build specification, create manual factory option for options that are not currently within Autoline. (This occurs where CESAR and Autoline franchise data are not synchronized). This can be created at franchise level within the build specification.
For migration purposes and setup it is assumed that ALL showroom enquiries will start using CESAR from the beginning. (Therefore there should be no conversion issues as there will be no enquiries on the system for new vehicles that have been created without using CESAR). For local stocks that are already stored in vehicle stock books it will still be possible to sell these through the showroom module, although no checks are made with CESAR.
