Workflow Triggers Table

Overview

The Workflow Triggers report presents a grid view of triggering conditions associated to each workflow. This can be any event or condition that exists as the first object in a workflow and used to "trigger" its execution based on a schedule or the occurrence of a specific event or condition.

The Workflow Triggers report can be used to keep track of all triggering objects that are linked to each workflow. It is specially useful in ascertaining which condition is used as a triggering object when numerous conditions exist in a single workflow or determining which workflows are being triggered by a particular condition in situations where a single condition is used as a triggering object in multiple workflows. This report supports exporting to multiple document types, column filtering, data grouping, sorting, filtering and more.

For complete instructions on how to use table reports, see Using Table Reports.

Related Topics

Data Sources

The Workflow Triggers report displays data in a two-dimensional table. The bound data is arranged in columns and rows. Grid columns correspond to data fields in a data source, rows represent data records. The table below lists the available data sources along with a brief description.

Column

Description

ID

The unique identifier of the workflow where the condition is used as a trigger.

Name

The user defined name of the workflow that contains the triggering condition.

Path

The full path to the triggering condition's location in the repository.  

Condition ID

The unique identifier of the condition used as a trigger.

Condition Name

The user-defined name of the condition used as a trigger in the workflow.

Condition Type

The type of condition that is used as a trigger in the workflow.

Filtering

This report can be filtered by columns which represent the data source and by repository item. In addition, a Filter drop down is available for column filtering and a Filter Editor is available for comprehensive filtering.

filter by Workflow

You can filter what appears in the report based on an individual workflow or group of workflows that belong to a specific folder.  To do this:

  1. Click the Repository drop-down button located on the right side of the Filter bar. A drop-down list of available workflows and workflow folders appear.

  2. Navigate to the folder or individual workflow you wish to include in the report. If a folder is selected, all workflows contained in that folder will be included.

To select a specific folder or workflow, follow the instructions listed in the table below.

To select...

Do this...

all workflows

Select Repository -> Workflows.

all workflows contained in a specified folder

Select Repository -> Workflows -> [folder name].

an individual workflow

Select Repository -> Workflows -> [folder name] -> [workflow name].

Filter Columns

The Columns button allows you to filter the columns to be included in the report. Columns vary depending on the report.

  1. Click the Columns button. A drop-down list of available columns appear.

  2. Select the columns to include in the report and deselect the ones to omit (omitted columns are unchecked).

NOTE: The list of columns to filter vary for each table-based report. The image above shows the available columns you can filter in the Workflow Triggers table.

Filter Column Data

The Filter button allows you to filter the data that appears for a certain column.

  1. Hover your mouse cursor over a column header and click the Filter button that appears.

  2. Select the column data to include in the report from the drop-down list.

NOTE: The image above is mainly used as reference to illustrate the location of the Filter button. The displayed data may not reflect the appropriate table.

Advanced Filter

The Filter Editor allows users to build complex filter criteria with an unlimited number of filter conditions combined by logical operators. To invoke the Filter Editor, right-click any column header and select Filter Editor. The Filter Editor displays filter criteria as a tree structure, where nodes represent simple filter conditions. If the filter criteria consist of multiple filter conditions, the Filter Editor contains multiple nodes linked by logical operators.