If the integration is on web service mode, messages between FieldEZ and the client application is over HTTP/HTTPS. All the APIs take input in key value pair style (not in REST style) and responds to the client in XML format. Authentication is through exchange of a login id/password combination maintained in FieldEZ as well as in customer application.
The payload request parameter in inbound API is XML. The name property of attribute element in payload XML should be configured as Integration Label of the respective workflow form element. This configuration can be done in web application. For example, if you have a workflow by name Maintenance with a form element Contact No, configure integration label as contactNo and pass the corresponding data in payload XML as 67243554423. This way, even if you later decide to change the display label, you could keep the same integration label, so that there is no change in integration client adaptor.
1. Save ticket
Type – Inbound
Use – Used to create or update a ticket in FieldEZ
Method – POST
URI – /emob/integration/saveTicket.action
Request parameters –
|payload||Ticket data in XML format. Please refer the sample XML and XSD attached here|
|apiKey||Login id for the client application||Yes|
|apiToken||Password for the client application||Yes|