Workflow management

Updated in 8.7

The Workflow and Business Logic > [Module] > [Object Class] > Workflow sections of the Sidebar allow you to organize full lifecycle of Alloy Navigator objects.

Each Workflow section consists of the following subsections:

NOTE: For additional information on workflow management, see Administration Guide: Workflow Management.

Actions

Actions are workflow steps that Alloy Navigator users (persons or services) perform when handling their tasks. Actions consist of Interactive Actions and Service Actions.

  • Interactive Actions are initiated by the user. Technicians access interactive Actions through the user interface. There are two types of interactive Actions:

    • Create Actions - These Actions are used to define how new objects are created. Every object must have at least one Create Action to allow creation, but you may have several to create different types of objects.

Technicians access interactive Create Actions through the New menu on the Module menu (above grids or in open object details windows) or from the File menu on the standard menu (File > New).

You manage Create Actions for a particular object class in the Workflow and Business Logic > [Module] > [Object Class] > Workflow > Actions > Create Actions section as follows:

Technicians access interactive Step Actions through the Actions menu on the Module menu (above grids or in open object details windows) or in the context pop-up menu on grids, or through the Action BarClosed (the Action Bar shows all Actions available to technicians according to technicians' roles and the lifecycle of the record they are working with) in open object details windows. In the Web App, technicians can also access interactive Step Actions by clicking the Actions menu icon in the leftmost column of the grid.

You manage Step Actions for a particular object class in the Workflow and Business Logic > [Module] > [Object Class] > Workflow > Actions > Step Actions section as follows:

      NOTE: Alternatively, you can create and modify Create Actions and Steps assigned to a specific Process in the Workflow and Business Logic > Advanced > Processes > [Process] section. For details, see Grouping Actions and Triggers into Processes.

  • Service Actions are non-interactive workflow steps initiated by Alloy Navigator servicesClosed (the Mail Connector, Alloy Discovery Connector, Active Directory Import tool, and the Self Service Portal) . There are two types of Service Actions:

    • Create Service Actions - These Actions are used to define how the service creates new objects. Create Service Actions are only available for certain object classes: Incidents, Problems, Change Requests, Work Orders, Computers, Hardware, Organizations, Locations, and Persons.

You manage Create Service Actions for a particular object class in the Workflow and Business Logic > [Module] > [Object Class] > Workflow > Actions > Service Actions section as follows:

    • Update Service Actions - These Actions are used to define how the service modifies already created objects. You configure Service Actions for a particular object class in the Workflow and Business Logic > [Module] > [Object Class] > Workflow > Actions > Service Actions section. Update Service Actions are only available for certain object classes: Incidents, Problems, Change Requests, Work Orders, Computers, Hardware, and Persons.

You manage Update Service Actions for a particular object class in the Workflow and Business Logic > [Module] > [Object Class] > Workflow > Actions > Service Actions section as follows:

Triggers

Triggers are non-interactive workflow items based on a condition or an event such as record creation, modification, or deletion. As opposed to Actions, Triggers are not dependent on the object's lifecycle stage or the particular workflow step.

There are three types of Triggers:

  • On Condition - These Triggers will fire when existing objects satisfy a specified condition. Alloy Navigator checks this condition at specific times. You may set a schedule to determine when or how often the condition is checked or configure Alloy Navigator to check the condition whenever an object is created or modified. These Triggers do not run on inactive objects, i.e. objects in "Closed," "Retired," or "Inactive" status.

  • On Created/Modified - These Triggers react to an object creation or modification. Unlike "On Condition" Triggers that check their condition after the object has been saved, "On Created/Modified" Triggers fire before the new data is saved into the database.

  • On Delete - These Triggers react to the event of an object's deletion.

You manage Triggers for a particular object class in the Workflow and Business Logic > [Module] > [Object Class] > Workflow > Triggers > [Type] section as follows:

NOTE: Alternatively, you can create and modify Triggers assigned to a specific Process in the Workflow and Business Logic > Advanced > Processes > [Process] section. For details, see Grouping Actions and Triggers into Processes.

Components

  • Workflow components - Just as there are several unique types of workflow items in Alloy Navigator, there are also four types of workflow components, which are the building blocks of workflow items:

    • Templates - Templates are used in Create Actions for assigning initial values to fields of newly created objects. Additionally, you can use Templates in Create Object operations within Functions.

You manage Templates for a particular object class in the Workflow and Business Logic > [Module] > [Object Class] > Workflow > Components > Templates section as follows:

    • Forms - Forms are used in interactive Create Actions and Step Actions for requesting user input through customizable pop-up dialog boxes or wizards. You design Forms to request only the information needed for a specific situation. Additionally, Forms allow you to specify suggested values for important fields, filter field values, provide instructions, and validate user's input.

You manage Forms for a particular object class in the Workflow and Business Logic > [Module] > [Object Class] > Workflow > Components > Forms section as follows:

      • ClosedTo add a new Form:

        1. Click New. The Action Form [FormName] window opens.

        2. TIP: If you want to base the new Form on an existing one, select the source Form and click Copy Item.

        3. Configure the Form. For details, see Configuring Forms.

        4. When done, click OK.

      • ClosedTo modify an existing Form:

        1. Select the Form in the list and click Open (or double-click it).

        2. Modify the Form. For details, see Configuring Forms.

        3. When done, click OK.

      • ClosedTo delete a Form:

        • Select the Form in the list and click Delete.

    • Functions - Functions be invoked by Actions, Triggers, and other Functions to perform various operations (for details, see Adding workflow operations).

You manage Functions for a particular object class in the Workflow and Business Logic > [Module] > [Object Class] > Workflow > Components > Forms section as follows:

    • E-mail Notifications - E-mail Notifications are used to communicate workflow-related events to the people involved in the business process. You can define notification templates and use E-mail Notifications as operations in Actions, Triggers, and Functions.

You manage E-mail Notifications for a particular object class in the Workflow and Business Logic > [Module] > [Object Class] > Workflow > Components > E-mail Notifications section as follows:

Depending on the type, each workflow item requires various combinations of workflow components. You can configure these components separately and link to them in workflow items.

    • Push Notifications - Push Notifications are workflow operations used to communicate workflow-related events to the participants of the business process. Push notifications appear as text messages on technician's mobile device to alert them about important events, such as ticket escalations or announcements. For details, see Configuring Push Notification.

    You manage Push Notifications for a particular object class in the Workflow and Business Logic > [Module] > [Object Class] > Workflow > Components > Push Notifications section as follows: