This method allows the adding of activity data.
URL : http://webservice.dealerhub.net/dealerhub/WS/DealerHubV1.cfc?wsdl
Method : addactivity
Input Parameters :
XMLSecurity
XMLData
There are always 2 parameters passed, these are both XML strings, and the first is XMLSecurity which holds the secuirty information, i.e your access code and the dealercode that you want to access the data for, and the second is the XML data you are going to pass in.
Input XML Data breakdown:
| Section |
Field Name |
Mand |
��Type |
Field Description |
Example Data |
| Activity |
CustID |
Y |
Numeric |
Your database ID number for the customer
the activity belongs to. You would have used this number already when
adding customer details using addcustomer method. If a number is passed
in that we do not have a customer record for, it will be rejected. |
12345 |
| Activity |
DiaryDate |
N |
Date |
The date the activity
took place, if not passed in, the system assumes todays date |
10/04/2013 |
| Activity |
ContactNumber |
Y |
Numeric |
The customer contact
number, i.e 1 = first contact, 2 = second contact etc.. |
2 |
| Activity |
Purpose |
N |
String |
The purpose / description
of what happened on this activity contact |
Follow up regarding
possible test drive of Adam |
| Activity |
VisitOut |
Y |
String |
Did a visit out of the
dealership take place on this activity? Pass Y or N characters |
N |
| Activity |
VisitIn |
Y |
String |
Did a visit take place
in the dealership on this activity? Pass Y or N characters |
N |
| Activity |
TelephoneOut |
Y |
String |
Did the salesperson
telephone out to the customer on this activity date? Pass Y or N characters |
Y |
| Activity |
TelephoneIn |
Y |
String |
Did the customer telephone
into the dealership on this activity date? Pass Y or N characters |
Y |
| Activity |
EmailOut |
Y |
String |
Did the sales staff
email out to the customer on this activity? Pass Y or N characters |
N |
| Activity |
EmailIn |
Y |
String |
Did an email come into
the dealership on this activity? Pass Y or N characters |
N |
| Activity |
TestDrive |
Y |
String |
Did a test drive take
place on this activity? Pass Y or N characters |
N |
| Activity |
Presentation |
Y |
String |
Did the sales staff
present deal figures to the customer on this activity? Pass Y or N characters |
N |
| Activity |
CollateralSent |
Y |
String |
Did give/send collateral
such as a brochure on on this activity? Pass Y or N characters |
N |
| Activity |
Appointment |
Y |
String |
Did an appointment take
place on this activity? Pass Y or N characters |
N |
| Activity |
ColdCall |
Y |
String |
Did a cold call take
place on this activity? Pass Y or N characters |
N |
| Activity |
Sale |
Y |
String |
Did a sale take place
on this activity? Pass Y or N characters |
N |
| Activity |
SaleVehicleNo |
Y * 1 |
String |
The SONO or Vehicle
number is required of the sale field = Y |
|
| Activity |
Delivery |
Y |
String |
Did a delivery take
place on on this activity? Pass Y or N characters |
N |
| Activity |
LostSale |
Y |
String |
Did a lost sale take
place on on this activity? Pass Y or N characters |
N |
| Activity |
LostSaleReason |
Y * 2 |
String |
Reason for the lost
sale, if lostsale = Y |
|
Y * 1= The SaleVehicleNo
is required if Sale is set to Y
Y * 2 = The Lost sale reason is required if LostSale
is set to Y
An example of value XMLData packet:
<Activity>
<custid>12345</custid>
<diarydate></diarydate>
<contactnumber>1</contactnumber>
<purpose>New customer enquiry</purpose>
<visitout>N</visitout>
<visitin>Y</visitin>
<telephoneout>N</telephoneout>
<telephonein>N</telephonein>
<emailout>N</emailout>
<emailin>N</emailin>
<testdrive>Y</testdrive>
<presentation>N</presentation>
<collateralsent>N</collateralsent>
<appointment>N</appointment>
<coldcall>N</coldcall>
<sale>N</sale>
<salevehicleno></salevehicleno>
<delivery>N</delivery>
<lostsale>N</lostsale>
<lostsalereason></lostsalereason>
</Activity>
|
Example output for a valid call:
<?xml version="1.0" encoding="UTF-8"?>
<ResultSet>
<MessageCode>1000</MessageCode>
<Messagetxt>Record Inserted Successfully</Messagetxt>
</ResultSet>
|
Example output for an invalid call / or general error in a webservice call
<?xml version="1.0" encoding="UTF-8" ?>
<ResultSet>
<Error>
<ErrorCode>2</ErrorCode>
<ErrorInfo>No data found </ErrorInfo>
</Error>
</ResultSet> |
There may be multiple errors returned in the XML packet, they are separated by <Error> blocks and each block contains an ErrorCode to allow you to do some processing logic on the numerical value returned, and an ErrorInfo which is used by the developer or administrator to visually see what the problem is with the submission.