Storing ticket data
Last updated
Last updated
You can also store data in Custom Fields which are created by your application. This method has the advantage that your Custom Fields can be used with Ticket Filters and Triggers to create powerful automations.
If you are not yet familiar with the concept of Custom Fields in Deskpro, head over to the official documentation:
You declare custom fields and their type in your application manifest. The custom fields are created when the application is installed and they become available through the Deskpro REST API and will also appear in the admin interface, where you can include them in Filters and Triggers.
Unlike regular custom fields, these custom fields can not be deleted while your application is installed.
Here is an example of declaring a Ticket Custom Field of type text with an alias and a title
Application Custom Fields are referred to by their alias
which must be always defined in your application manifest. The following snippet shows you how to write and read a custom field using the Custom Fields Client:
For in-depth coverage of Custom Fields definition, see the section from the Manifest reference.
The allows you to read and write custom field values from the Deskpro Object
specific to the target in which the application is running. It can work for both regular Custom Fields and Application Custom Fields.
For more usage examples, see this recipe: