This page aims to provide our customers with transparency how the server side API access is used for the Due Time app. Changes to the app that affect information provided in this document will also be posted in the comments section below. Should you want to be aware if this information changes, please register on this help center and follow this page.
|Tickets||X||X||Fields that may contain personal information of end users aren't stored|
|Triggers||X||Optional ability to create trigger when setting up a new workflow|
|App Installation||X||Initialization only (setting secure token)|
|Resource collections||X||Initialization only (setting secure token)|
The Due Time app performs the following changes within your Zendesk account only:
- During initialization, a secure account token is set in the app's installation settings and the built-in target, updated via the resource collection API.
- Due Time tags tickets on which a deadline was created at various times to enable workflow and reporting on those tickets, examples include due_pending, due_now.
- When creating a new Workflow record, an option to create a trigger is available as convenience.
No further write operations are carried out by the Due Time app.