Forms

Creating a form

For these, you will need to create a corresponding form file in the sync repo.

You should also do this in a way that creates a MR. Said MR should always be peer reviewed before merging (the MR should enforce this).

The exact nature of what you need to put into the YAML file will vary based on the issue’s request.

Be sure to read Working with sync repo files for more information.

Editing a form

For these, you will need to locate the corresponding form file in the sync repo and make changes to it.

You should also do this in a way that creates a MR. Said MR should always be peer reviewed before merging (the MR should enforce this).

The exact nature of what you need to put into the YAML file will vary based on the issue’s request.

Be sure to read Working with sync repo files for more information.

Deactivating a form

To deactivate an form, you must make the following changes in the corresponding form file in the sync repo:

1. Move the form file from the active folder to the the corresponding location in the inactive folder (if it does not exist, create it)

2. Change the value of the active attribute in the YAML file to false

3. Change the ticket_field_ids seciton to be:

   - 'Status'
   - 'Group'
   - 'Assignee'
   - 'Ticket status'
   - 'Subject'
   - 'Description'
   

4. Change the end_user_conditions section to be []

5. Change the agent_conditions section to be []

You should also do this in a way that creates a MR. Said MR should always be peer reviewed before merging (the MR should enforce this).

Deleting a form

The process to delete a form is exactly as described in the forms documentation page.

Exception deployment

To perform an exception deployment for forms, navigate to the forms project in question, go to the scheduled pipelines page, and click the play button. This will trigger a sync job for the forms.

Repo links

• Zendesk Global sync repo
• Zendesk US Government sync repo

View page source - Edit this page - please contribute.