Configure workflow

Once you finish deploying the workflow template, the following steps will guide you through the process of configuring your workflow.

1. Access existing rule: From the Foundry Rules home page, choose from a list of existing rules by selecting the item. Alternatively, you may also navigate and select it from its respective project found in Files.

   

2. Add workflow inputs: With the rule in view, select the Add Input button to add an object or dataset input to the workflow. This will become usable as an input to the rule authored in the next section.

   • You can add as many inputs here as you wish, but all workflows must contain at least one input.
   • When adding object type inputs, the link types section will appear below each object type. Any links selected will become usable in the Rules Management application for joining together different objects.

   

3. Add workflow outputs: In the third section of the editor, click Add Dataset Output and provide a name and location for the dataset where the rule results will be output.

   

   • Provide a name for the output that will be displayed to rule authors in the Rules Management application (a).
   • Click Add column to add at least one column to the output (b). Give this column a name to be used in the dataset and a display name to show to rule authors in the rules application. You can configure the type of column and determine whether it is required to provide this column when authoring a rule. Learn more about permitted and default output values.
   • Add a column for each piece of information you wish to capture from the results of your rule. For example, an alerting workflow may have columns for Alert ID, Severity, and Assignee as well as a column to capture an identifier for the object that triggered the alert (e.g. Machine ID).

   

4. Save the workflow: In the top right of the configuration editor, click the save button.

   • After saving the workflow, you should see a green banner appear at the top of the editor, signifying that the transforms pipeline has been created successfully.

   

After completing the above steps, learn how to author and run a rule.

Advanced configurations

Alternate backing datasets

You can configure an object input with an alternate backing dataset. This means your rules are evaluated against the supplied alternate backing dataset instead of the writeback (or backing) dataset configured in the Ontology.

This is useful when:

• Writing rules on restricted view-backed objects
• Running rules on a subset of the Object's backing data