Page History

 You can configure a ticket workflow to generate any of the following events:

• Send an email or SMS
  
• Create a work queue task
• Update a field in a ticket
• Call an API function
• Stop the workflow

The Workflows tab displays the following subtabs:

enables you to create a workflow

for the form, the tab consists of the following subtabs:

• Design: Enables you to configure a workflow.
• Activity: Enables you to view all the tickets to which a workflow is applied.

• History: Enables you to view all the changes made to a workflow.

To create and design a workflow:

1. On the Workflows subtab of the Workflows tab, click New event.
   
2. Specify values in the fields, and then click Save.
   The ticket workflow is created, and the Design subtab appears.

3. Click New Event.

4. Specify values in the following sections, as required:
   

   • Involves these events: Actions when you want the workflow to be triggered (for example, when the ticket is created or updated, or when a nightly run is initiated). If you select the Update Ticket trigger, the workflow is triggered only when a specific field in the ticket is updated.
     
   • Tickets with these properties: Properties for the tickets on which you want the workflow to be applied. The default value is Always, which indicates that the workflow is applied to tickets regardless of their properties. You can modify the value by using the Edit button.
     
   • Perform these actions: Resulting actions for the workflow, such as:
     • Send SMS: Sends an SMS.
     • Send Email: Sends an email.
     • Create WQ Task: Creates a work queue task.
     • Update Ticket Field: Modifies the value in a field in the ticket. 
     • Call Function: Calls an API function.

     • Stop Workflow Execution: Stops the workflow.
       After you specify a value in the Action Type field, click Add, and then specify values in the fields that appear.
       

       Info

       When you add the Send SMS action, the Send SMS to section appears, displaying the following fields: Template: Enables you to select an SMS template. The message in the selected template appears in the section. To: Enables you to specify a phone number or select one of the following options: contact.phone1: Phone number of the contact associated with the ticket. ticket.phone1: Primary phone number associated with the ticket. ticket.phone2: Secondary phone number associated with the ticket. When you add the Send Email action, the Send EMAIL to section appears, displaying the following fields: Template: Enables you to select an email template. The message in the selected template appears in the section. To: Enables you to specify an email address number or select one of the following options: contact.email: Email address of the contact associated with the ticket. ticket.email: Email address associated with the ticket. CC and BCC: Enables you to add CC and BCC email addresses. This is available in both Template and free-form options. When creating a work queue task, you can specify the due date and due time for the task. You can delete an action by using the delete iconnext to the action.

       
       

     
     

5. Click Save.
   The workflow is designed, and the event appears on the Design subtab.

   Info

   For the same event (Create Ticket, Update Ticket, or Nightly Run), you can add another design (that is, specify additional ticket properties and actions for the workflow) by using the plus icon  next to the event. You can modify a design by using the pencil icon  next to the design. You can add another event by using the New Event button. You can delete an event by using the delete iconnext to the event.

   
   

To view all the tickets to which a workflow was applied, on the WORKFLOWS subtab of the Workflows Workflows tab, double-click the workflow for which you want to view the tickets, and then click the Activity subtab.
A table with the tickets to which the workflow was applied appears. The table displays the following columns:

• Version: Version of the workflow that was applied to the ticket.
  
• Executed at: Date and time when the workflow was applied to the ticket.
  
• Ticket: Number of the ticket.
  
• Ticket Name: Subject of the ticket.
  
• Event: Event (trigger) when the workflow was applied to the ticket (that is, when the ticket was created or updated, or when a nightly run was initiated).
  
• Condition: Properties of the ticket that determines if the workflow is applied to the ticket. The value Always indicates that the workflow was applied to the ticket regardless of its properties.
  
• Action: Action resulting from the workflow.
  
• Action Body: Information about the action.
  
  

To view all the changes made to a workflow (including its design), on the WORKFLOWS subtab of the Workflows tab, double-click the workflow for which you want to view the changes, and then click the Change History subtab.
A table with the changes appears, displaying the following columns:

• Version: Version of the workflow on which the change was made.
  

  Info
  If any change is made to a workflow after it is published, the version of the workflow is incremented.

  
  

• Changed on: Date and time of the change.
  
• Updated by: ID of the user who made the change.
  

• Entity: Entity that was changed.
  

  Info
  The value WORKFLOW indicates that the workflow was changed. The value TRIGGER indicates that the design of the workflow was changed.

  
  

• Ticket Type: Section of the workflow design that was changed.
  

  Info
  The value EVENT indicates that the Involves any of these events section of the design was changed. The value CONDITION indicates that the On tickets with these properties section of the design was changed. The value ACTION indicates that the Perform these actions section of the design was changed.

  
  

• Operation: Type of change made to the workflow (for example, create, update, publish, unpublish, or delete).
  
• Details: Description of the change.