/
Is it broken? Or is it designed that way?

Is it broken? Or is it designed that way?

Apr 07, 2016

Please add to this page as you get issues submitted, but it is actually how the system works. Also update if the system is changed to behave differently. Please check here if you are seeing a behavior in the system that may actually be a design thing rather than a bug thing.

  1. Rebates & Incentives Disappear
  • The system will first check if the appropriate location has Payment Driver incentives turned on. It determines which location to check based on whether a CarID is provided, or if a LeadID/DealID is provided. If only a CarID, use the vehicle location. If a LeadID/DealID, use the location of the agent assigned to the lead. Once the system determines the location is configured for Payment Driver it then verifies the vehicle has a ChromeStyleID (is chrome matched). The system will not check for incentives if the vehicle is not chrome matched. If the vehicle is indeed chrome matched, the system will make a request to our server with the following information: CustomerID, CarID, LocationID, StyleID (ChromeStyleID), and ZipCode. The ZipCode value is determined by whether a customer is present or not. If there is a customer and they have a zip code, the system will use that. If the customer does not have a zip code it will use the current users zip code from their location in the system. The system will attempt to retrieve incentive data given all of the provided information from the Payment Driver web service. If no incentives are returned from the web service, the buttons will not display.
  • Provided example 1 (Customer Merla Test 1 http://beavertoyota.virtualdeal.com/?fuseaction=Desk.DealScreen&DealID=&LeadID=3D926FAA-04D3-2916-6858-2426EF0D94EE&CarID=ACA08629-6A05-4C0A-0102-0000015C05C7&Layout=Popup): Programs are not showing for the example provided because the zip code entered (98652) is not a valid zip code. I Googled that zip code and entered it into several tracking sites like USPS and they all told me it's not a valid zip code. I used our Chrome Debug tool (http://www.dealerpeak.com/?fuseaction=Administrator.ChromeDebug#/2016/39/28926/381196/) and also manually requested the data from the Payment Driver web service and received no results.
  • Provided example 2 (Car only http://beavertoyota.virtualdeal.com/index.cfm?fuseaction=Desk.DealScreen&CarID=ACA08629-6A05-4C0A-0102-0000015C05C7&Layout=Popup): This example did work because it used the zip code (32086) from the location.
  • Issue example VDEAL - 135