Vanilla 1.1.9 is a product of Lussumo. More Information: Documentation, Community Support.
1 to 8 of 8
i played a bit with the rest api and tryed to get the last ticket with a specific word in it, but i havent found out how to reference the ticket request detail. is there anywhere a list of supported attributes for the api? i only found locationnam, firstname and lastname in the api documentation
You can get the full API spec here:
please read the api documentation. the only attributes i found are location.locationName, firstName and lastName. is that all or is there something missing in the documentation?
You should be able to use any of the attributes that are in the ticket section. To search for some text in the request detail try using:
This should bring up any "Recent" tickets that have "SEARCHTERM" in the Request Detail fields.
Ok, I can query the fields in the ticket itself. Is it also possible to query customFields that are applied to the ticket?
I tried: http://127.0.0.1:8081/helpdesk/WebObjects/Helpdesk.woa/ra/Tickets.json?username=***&password=***&qualifier=%28ticketCustomFields.restValue%3d%27123%27%29 and it returns:
sqlStringForKeyValueQualifier: attempt to generate SQL for com.webobjects.eocontrol.EOKeyValueQualifier (ticketCustomFields.restValue = '123') failed because attribute identified by key 'ticketCustomFields.restValue' was not reachable from from entity 'JobTicket'.
Looking at the current API documentation at <a href="http://downloads.webhelpdesk.com/api/#cf"> http://downloads.webhelpdesk.com/api/#cf</a> you will first need to get the list of the custom fields which will the give you the customField_<id> identifier.
At the bottom of <a href="http://downloads.webhelpdesk.com/api/#tickets-create">http://downloads.webhelpdesk.com/api/#tickets-create</a> they show an example of creating a ticket with custom field information.
I know my customField id, but I want to search for a ticked based on the value of the custom field.
Can you please provide a sample request that will return tickets that have the customField_1 value equal to '123'
Feel free to log a support ticket