Ticket Workflows

Owned by UdayKiran.Guduri (Unlicensed)
Last updated: Feb 20, 2018 by priti.hota (Deactivated)

Once a ticket is submitted in Intelligent Service Management, either through the Service Catalog or Ticket Center workspace, a process workflow is automatically selected and applied to it by Intelligent Service Management's routing engine in order to control how the ticket's lifecycle is managed. The process workflow selection is based on matching data entered on the new ticket form and matching criteria defined in a process workflow. Matching criteria is based on ticket attributes like a priority value, the requester's organization, a VIP user, or categorization. There is also a sort order assigned to process workflows to guide the engine to which workflows to check for matching criteria first. When the first match is found, the routing engine stops checking and assigns that workflow to the ticket. 
Many default process workflows are included with Intelligent Service Management. One example is the Default Incident Management Process. Out of the box, you will see this process being added to all new incidents under the incident's Activity History.

 
The Default Incident Management Process flow is not directly linked to any Service Catalog Item, but in a new system it will be automatically selected because the process workflow does not have any initial entry criteria rules defined to match on, as seen in the below screen shot, and will therefore match all entry criteria. It is also the only published workflow for incidents.

 
When reviewing the default process workflow for an Incident, refer to the documentation wiki here. You may want to modify the Default Incident Management Process Flow in order to support your business flows and necessary initial incident assignments.

Review the Default Incident Management Process

Take time to review how the default incident management process works, and update it as necessary to support your own assignment requirements and incident workflow.

  1. Log in to the Intelligent Service Management as an Administrator
  2. Navigate to MANAGE> ADMINISTRATION>  Tools> Process Workflows
  3. Select the Filter button and under Form Type select Incident
  4. Click Apply
  5. To the left of Default Incident Management Process Flow, select Checkout for Editing
  6. Select Yes, checkout for editing
  7. Select the Process Designer channel button
  8. Review the Basic Properties button fields:
    1. Form Type means a Process Flow is associated with one particular type of ticket
    2. Tags to categorize are a convenient and useful way to categorize the Process Flows and easily filter or retrieve these specific workflows later.
  9. Click the Process Designer button to open the graphical UI for building Process Flows. Note the workspace on the left and the Edit panel on the right.
  10. Minimize the Edit panel but clicking the  button.
  11. Zoom out and back in by clicking on the  icons.
  12. Use the scroll bars on the right and the bottom of the workflow window to review the different steps and branches.
  13. Click the Back To Top  icon.
  14. In the left side panel, select the top box, Entry Criteria - Incident.
  15. Move your mouse over the information icon  to get a summary of the step and how it is configured.
     
  16. The Edit Step tab displays on the right side with the Define channel button selected. This is where the workflow step is configured.
  17. Look at the fields on the Define channel button:
    1. Entry Criteria: conditions that must be matched for this workflow to drive an incident. In this case, there are no matching conditions.
    2. Sort Order: as with existing auto route functionality, this field will dictate when the entry criteria is evaluated.
    3. Type: Auto Route is selected by default, and is indicated by the icon and blue color coding of the Step. By default there is no Entry Criteria for this workflow as defined in the Rapid Workflow Implementation Guide. The additional option, Auto Route with Workflow Action, can be used to trigger an immediate action after the request is submitted by the user, such as automatically creating associated tasks, or approvals.
    4. Check for conflicting process flows: hyperlink to assist in finding overlapping conditions. 
  18. Click the Assign channel button.
    1. The Group that will be assigned to Incident tickets by default is the Service Desk (L1). Change the default group to one of your own if you do not have the default group populated with analysts.
       
    2. There is no defined User assignment for this process.
    3. The Auto Assignment "assign" rules are defined here. They state to assign the Service Desk (L1) group if the source is not equal to Scratchpad or Agent. This way, when an analyst manually opens an incident for an end user, the analyst will become the default assignee and not the Service Desk (L1) group.
  19. Click Set channel button.
    1. Ticket attribute values can be defined here and will be set when this step in the Process Workflow is completed.
    2. Select the  icon to remove any attributes you don't want set. Traditionally, Phase, Reason Code, and Status are used to set ticket lifecycle status and to drive behavior in the workflow.
    3. Select the  icon to add additional fields you would like to set when an incident is created.
  20. Click the Notify channel button.
    1. This is where notifications, or communication templates, are related to the workflow action.
    2. The IncidentAuto-Route (Web) is used in this example. Change the associated communication template if needed.
  21. Click on the second workflow step in the left side pane, Accept New Incident.
    1. Hover your mouse over the Information icon.
    2. The pop-up summary will show an overview of the configuration for this step. Also notice the different paths, or connected steps, that are available at this stage in the Process Flow. These become highlighted with dashed orange lines.
  22. Click the Show Advanced Options hyperlink.
    Notice the ability to set Mandatory Fields, attach Web Service Operations (like sending a request to a 3rd party Service Desk or to another system) and the ability to configure how this Workflow Process Step will work when the ticket is a Child ticket.
  23. Click the Permissions channel button.

    This step will be available to the Administration group and any user with the Incident Manager role when working the incident.
  24. Click the Set channel button to view the Ticket Parameters, or attributes, which will be set during this workflow step.
  25. Click the Notify channel button. The default communication template, Incident_Accepted, is set for this step. 
  26. Optionally, continue exploring the configuration of additional steps.
  27. Click Back To Top.
  28. If you made changes, click Save and Re-Publish, otherwise, close the Default Incident Management Process Flow without saving it.

Review Common Ticket Actions

Aside from using Process Workflows to present actions to analysts to use during a ticket's lifecycle, common ticket actions present additional common actions without the restriction of being defined in a process workflow. Common ticket actions are either defined as bulk actions, which will work across all ticket types or are defined for a specific type of ticket only. 
Unlike actions defined in a process workflow, Common Ticket Actions are always visible on a ticket no matter what the ticket phase is in since they do not have matching conditions. 
Intelligent Service Management has 24 default common ticket actions available. They can be seen by navigating to MANAGE> ADMINISTRATION> Tools> Process Workflows and clicking on the Common Ticket Actions channel button. The below screen shot shows the incident specific common ticket actions circled. 
 
Similar to actions defined in a process workflow, common ticket actions are defined with permissions at the role, group, or contact level. They can be used to set attribute values and trigger notifications. 
Common ticket actions will show up in the Ticket's list on the Ticket Center Workspace, and in a ticket detail form. 
Ticket Center
The Ticket Center Workspace has a Tickets list area with a Bulk Actions drop down button used to present relevant actions to the logged in analyst or administrator. When case numbers, or tickets, in the list are selected, Bulk Actions becomes available, as shown below. 

 
Ticket Detail
When an analyst is working in a ticket detail form, the Actions drop down menu will present actions from:

  • The process workflow in play
  • Common ticket actions defined for the type of ticket the analyst is looking at
  • All Bulk Actions
  • System defined actions that are always there and not modifiable.

The following screen shot shows an incident's Actions list noting where the action is derived from. 

Applying Process Workflows

After you have created, reviewed, updated, and tested process workflows to support your business, you are ready to apply them to tickets. 
There are several ways to instantiate your business process. 
Directly from a Service Catalog Item
When an end user or analyst selects an item from the Service Catalog, it may be directly linked to a process flow, as shown below. 

Attaching a specific process flow to a catalog item will ensure that the correct process will be applied to the ticket. 
From the New Ticket
Analysts using Intelligent Service Management from the Ticket Center workspace can create new tickets by selecting an option under the Actions drop down. For example, ActionsNew Incident.  
When the new ticket form appears, the analyst is free to start entering data about the requester and capture the nature of the incident. During this process, if there is a relevant Service Catalog Item that has a matching workflow, it can be selected from the new ticket's Actions menu. The screen shot below shows the Report an Outage service catalog item being selected to apply to the new incident. 

All default information will be applied to the new incident such as default attribute values, process workflows, and routing. 


Matching Criteria
When an analyst or end user enters data in a ticket, that data is used to match against entry criteria in process workflows. Refer to the documentation wiki here for information on entry criteria. 
The following screen shot shows a ticket with a description that matches the matching condition in a process workflow's Entry Criteria tile.

Example: Create a New Service Request Process Workflow

In this example, we will create a new Process Flow that handles the process for Service Requests for a Virtual Machine with an Oracle DB installed. Oracle DB requires a license and thus requires approval from management.

Create Pre-requisite data for this example

In order to create process flows, you will need to be logged in as an Administrator. The example uses data that will not exist in a new slice, so the steps to create the supportive data follows. 
Categorization: Infrastructure Services > Server > Provision/Add > Virtual Guest Machine
A new category will drive the assignment of the sample workflow.

  1. Navigate to MANAGE> ADMINISTRATION> Tools> Categorizations
  2. Click the New Categorization button
  3. Enter Class: Infrastructure Services
  4. Enter Category: Server
  5. Enter Type: Provision/Add
  6. Enter Item: Virtual Guest Machine
  7. Select Service Request
  8. Select Save

Group 1: Infrastructure (L2)
A new group will be used for initial default assignment of the Service Request.

  1. Navigate to MANAGE> ADMINISTRATION> Tools> Groups
  2. Select New Group
  3. Group Name: Infrastructure (L2)
  4. Description: Test group for new process exercise
  5. Used for: Permission, Approval Group, Notification, Assignment
  6. Group Email: <enter a valid email address if you want to test notifications>
  7. Select the Members Channel button, and add yourself as a member and one or two other contacts to test with
  8. Click Save
  9. Under the Members tab, enter yourself and optionally another analyst

Group 2: Database Administration
A second group will be used for conditional assignment.

  1. Navigate to MANAGE> ADMINISTRATION> Tools> Groups
  2. Select New Group
  3. Group Name: Database Administration
  4. Description: Test group for new process exercise
  5. Used for: Permission, Approval Group, Notification, Assignment
  6. Group Email: <enter a valid email address if you want to test notifications>
  7. Select the Members Channel button, and add yourself as a member and one or two other contacts to test with
  8. Click Save
  9. Under the Members tab, enter yourself and optionally another analyst

Custom Attribute: Select Database Server Type
A new field on the form will hold information gathered from the end user.

  1. Navigate to MANAGE> ADMINISTRATION> Tools> Custom Attributes
  2. Click Create New
  3. Attribute Name: Select Database Server Type
  4. Attribute Type: List
  5. Possible Values: Oracle 10G~Oracle||Microsoft SQLSQL||MySQL~MySQL
  6. Click Apply Changes

Custom Ticket Attribute Template: SR for Virtual Machines
A new Custom Ticket Attribute Template will link the custom attribute to the new categorization so that it will be available to the end user whenever the category is selected on the ticket form.

  1. Navigate to MANAGE> ADMINISTRATION> Tools> Custom Ticket Attribute Templates
  2. Click Create New
  3. Enter:
    1. Related To Form: Service Request
    2. Template Name: SR for Virtual Machines
  4. Click Apply Changes
  5. In the lower half of the form, select the Attribute Name: Select Database Server Type
    1. Select Visible To Self-Service User
    2. Select Save Attribute at the bottom of the form
    3. Click the Related CCTI Tab
    4. Search for the CCTI added earlier and click Add CCTI.

Service Catalog Item: Virtual Machine Request
Service catalog items act as templates in Intelligent Service Management where pre-defined field data and workflow behavior can be defined. The catalog items are made available to users with assigned permissions from the Service Catalog. In our case, we will create a service catalog item and pre-define the categorization, or CCTI. To do this:

  1. Navigate to MANAGE> ADMINISTRATION> Tools> Service Catalog Configuration
  2. Select New Catalog
  3. Browse for an icon by selecting Browse…
    Note, default icons can be downloading in a zip file here. These are helpful in building out your catalog.
    Enter:
    1. Catalog Name: New Virtual Machine Request
    2. Describe Your Catalog: Use this catalog item to request new virtual machines for application testing.
    3. Ticket Type: Service Request
    4. Which category does this belong to?: IT Services
      Note: This is not related to CCTI, it is the service catalog categorization for items listed.
  4. Select Save & Proceed To Next Step
  5. Under the Define Attributes section, Populate the Categorization with: Infrastructure Services » Server » Provision/Add » Virtual Guest Machine
  6. Select Save & Proceed To Next Step
  7. Under the Viewers section, enter the Self-Service Group
  8. Click Save and Exit, as we will attach the process workflow later.
  9. Test the Catalog Item by navigating to WORKSPACES> SERVICE DESK> Service Center
  10. Select the catalog item, New Virtual Machine Request
  11. Enter:
    1. Requester: Enter your name as the Requester
    2. Description: Testing new catalog item
      Notice that the Categorization is pre-set with our new CCTI, and under Additional Information, the new custom attribute is listed.
    3. Select Database Server Type: Select Oracle 10G for the attribute value.
    4. Select Save & Exit
      View your new ticket under the My Tickets tab.
  12. Open the ticket by double clicking on it.
    You will see that the ticket is assigned to the group Service Desk (L1), unless you changed the default assignment group on the Default Service Request Management Process Flow. 

Role Based Views: Default View for Service Request
In order for approval statuses to be seen on Service Requests, we will need to ensure that the default role based view has the Approval section selected to show. By default this section header is not viewable on Service Request forms. 
Update the default View for Service Requests.

  1. Navigate to MANAGE> ADMINISTRATION> Tools> Role Based Views
  2. Select the View Name: Default View For Service Request
  3. Under Section Header, select Show next to Approval
  4. Click Apply Changes
     
    Note: You will need to log out and back into Intelligent Service Management for the form change to take effect.

Create Service Request Process Workflow

In this example we will create a process to handle service requests for virtual machines. We will create an assignment routing rule, and if the user is requesting an Oracle DB, we will move the ticket through an approval cycle before the fulfillment of the request.

  1. Navigate to MANAGE> ADMINISTRATION> Tools> Process Workflows
  2. Click New Process Flow.
  3. Complete the fields:
    1. Process Flow Name: VM with Oracle DB
    2. Description: New process to manage requests for VMs using Oracle.
    3. Form Type: Service Request
    4. Tags to categorize: <start typing 'vm' to get a list to choose from> select vmware
  4. Click Save & Proceed
    The entry criteria box will automatically be in focus, Entry Criteria - Service Request.

    In the right panel, the Edit Step is displayed with the  channel selected.
  5. Click the dropdown box numbered 1.
  6. Select Categorization.
  7. Click Search icon 
  8. Select Infrastructure Services > Server > Provision/Add > Virtual Guest Machine.  
  9. Add a Sort Order value of 100.
    Note: Sort Order is important as the first Process Flow that has matching Entry Criteria is executed unless it is exclusively associated with a Service Catalog item.
  10. Click Save Step.
  11. Click the  channel. Enter:
    1. Group: Infrastructure (L2)
    2. Click 
      The Auto Assignment Rule dialogue window will be displayed.
    3. Click the dropdown box labeled 1.
    4. Locate Select Database Server Type as the value for the Custom Attribute. The filter results will update as you start typing the letters.
      NOTE: Custom attributes will only show in the list once they have been tested on a ticket and populated at least one time. If your attribute is not in the list, make sure to test it using the pre-requisite steps above for linking custom attributes to categories through Custom Ticket Attribute Templates.
    5. Select Oracle 10G from the right dropdown box.
    6. Click Next
    7. Select Database Administration from the Group dropdown list.
    8. Click View Advanced Options.
    9. Under Set Fields:
      1. Select: Reason Code
      2. Value: Assignment Validation
    10. Click Add Rule
  12. Click Save Step.
  13. Click the Add Step tab
  14. Hover your mouse on each item in the All Steps list to see the available options:
    • Approval: use to define this step to submit or withdraw the ticket to/from approvals
    • Assign To: allows this task to set assignment to an individual or a group
    • Auto Assign: use to initiate the auto assignment engine for reassignment
    • Execute Automation Connector: use to call an automation center process
    • Create: use to create a new related ticket type from this ticket
    • Other: use to delete or check for open tasks
    • Update Ticket: used to insert a function that will update values on the ticket.
  15. Click Approval, then Submit For Approval
  16. On the Edit: Submit for Approval form, update the following:
    1. Name: Oracle DB Approval
    2. Description: Approval step submission for license key.
    3. Sort Order: 5
  17. Click Show Advanced Options and enter:
    1. Match Conditions Below: Select Database Server Type = Oracle 10G
    2. Approval Phase: Oracle DB Approval Phase
    3. Approval Status: License Approved
    4. Approval Type: Any One Approver
    5. Mandatory Fields: Cost Center
    6. Click Save Step
  18. Click the Approvers channel. Enter:
    1. Contextual Approvers: Assignment Group
    2. TIP: Click Close when you have selected the appropriate item(s) from the list.
    3. Add Additional Users As Approvers: <any user name>
    4. TIP: Start typing in the drop down field to filter the list.
    5. Add Additional Groups As Reviewers: Database Administration, Infrastructure (L2)
    6. Click Save Step
  19. Click the Permission channel. Complete:
    1. Who can trigger this step: Add Infrastructure (L2), Database Administration
    2. Click Save Step
  20. Click the Set Channel
    1. Set Ticket Parameter: Reason Code = Pending License Approval.
    2. Click Save Step
  21. Review the Step configuration by hovering your mouse over the Information icon.
     
  22. Click the On Approval tile in the left pane
  23. Select Update Ticket from Select Step Type dialogue box
  24. Define Basic Properties for the step:
    1. Name: Oracle DB Approval
    2. Description: Update ticket
    3. Click Save Step
  25. Click the Permission channel. Complete:
    1. Who can trigger this step: Add Infrastructure (L2), Database Administration
    2. Click Save Step
  26. Click the Set Channel
  27. Set the following Ticket Parameters, and click  to add new fields:
    1. Assign to Group: Infrastructure (L2)
    2. Phase: Fulfillment
    3. Reason Code: Oracle DB Approved
    4. Status: Approved
    5. Click Save Step
  28. Click the On Reject tile
  29. Select Update Ticket from Select Step Type dialogue box.
  30. Define Basic Properties for the step:
    1. Name: Oracle License Denied
    2. Description: Update ticket
    3. Click Save Step
  31. Click the Permission channel. Complete:
    1. Who can trigger this step: Add Infrastructure (L2), Database Administration
    2. Click Save Step
  32. Click the Set Channel
  33. Set the following Ticket Parameters, and click  to add new fields:
    1. Status: Closed
    2. ReasonCode: NOT Approved
    3. Phase: Cancelled
    4. Click Save Step
    At this point you could build out the fulfillment process with Automation Center to automate the fulfillment of the request once it is approved and additionally close the ticket automatically. For this example, we'll manually create a final Fulfillment Complete step to close out our process workflow.
  34. Select the Oracle DB Approval tile
  35. Click the Add Step tab
  36. Select Update Ticket from Select Step Type dialogue box
  37. Define Basic Properties for the step:
    1. Name: Complete Fulfillment
    2. Description: Close ticket
    3. Sort Order: 2
    4. Click Save Step
  38. Click the Permission channel. Complete:
    1. Who can trigger this step: Add Infrastructure (L2), Database Administration
    2. Click Save Step
  39. Click the Set Channel
  40. Set the following Ticket Parameters, and click  to add new fields:
    1. Status = Complete
      1. Reset status to: Closed
      2. After 1 days
      3. Reason Code: Auto Close
    2. ReasonCode = Fulfilled
    3. Phase = Fulfillment Complete
    4. Click Save Step
  41. Hover your mouse over the Entry Criteria and when the small dot appears at the bottom, click it and drag it to the Complete Fulfillment tile.
  42. Reposition your tiles to make the process easier to visualize
  43. Click Save on the top menu bar
  44. Click Publish
  45. Click Yes, check for conflicts
  46. Click Check Conflicts
  47. Click Ok
  48. Click Publish Process Flow

Link Process Workflow to Service Catalog

A Process Workflow will apply to any ticket that meets the Matching Criteria. If more than one process flow matches, the one with the lowest entry criteria sort order will be applied. In our example, Categorization must equal Infrastructure Services > Server > Provision/Add > Virtual Guest Machine. 
Additionally, you can link a Process Workflow directly to a Service Catalog item. Let's add our new process flow to the Service Catalog Item we created in the pre-requisite steps.

  1. Navigate to MANAGE, ADMINISTRATION, Tools, Service Catalog Configuration
  2. Search for and Select New Virtual Machine Request
  3. Click the anchor link for 
  4. Search for and select the new process flow: VM with Oracle DB
  5. Click  to go back to the top
  6. Click Save and Exit

Test the Process Workflow

  1. Test the Catalog Item by navigating to WORKSPACES, SERVICE DESK, Service Center
  2. Select the catalog item, New Virtual Machine Request.
    This time it should show up in the Most Common Items:
  3. Enter:
    1. Requester: Enter your name as the Requester
    2. Description: Testing new process workflow
    3. Select Database Server Type: Oracle 10G
  4. Select Save
    This time notice that the Owner is Database Administration, and not Service Desk (L1), and the Reason Code is Assignment Validation.
  5. Click the Actions Drop down and select Oracle DB Approval
  6. You should receive a notice about a required field that we set on this workflow action: Cost Center.
  7. Enter a text value for Cost Center and select Oracle DB Approval from the Actions list again.

    NOTE: You can inactivate the default Service Request fields by modifying the Custom Ticket Attribute Template named Default Custom Fields for Service Request.
  8. When presented with the list of approvers and reviewers, select yourself and any others from the list.
  9. At this point, the ticket is in the approval phase and cannot be edited.

    Note, the locking of tickets during approvals is controlled with the Configuration Parameter of LOCK_TICKET_DURING_APPROVAL.
  10. Select the Approvals anchor link to view the list of approvers
  11. Close the Service Request window
  12. Navigate to WORKSPACES, SERVICE DESK, Outstanding Items
  13. The approval task should be listed under the Approvals section. Select the task and approve it.
  14. Navigate back to the My Requests tab and open the test Service Request ticket
  15. Validate that the Group Assignment, Phase, Status and Reason Code have been updated
  16. Select *Actions->Complete Fulfillment*
  17. Validate that the Phase, Status and Reason Code have been updated
  18. Open a new Service Request from the Service Catalog and test the path of Rejecting the approval.
  19. Open a new Service Request and test assignment when Oracle 10g is not selected. Ex. the group assigned should be Infrastructure (L2), and no approval option is presented.

© 2019 Serviceaide 1-650-206-8988 http://www.serviceaide.com info@serviceaide.com