# Foundry Rules workflow configuration

The **workflow configuration editor** is used when making changes to how the entire Foundry Rules workflow is configured; for example, when adding new [inputs](../rule-logic/index.md#inputs) so that they may be used by rule authors, or when modifying [workflow outputs](#workflow-outputs). The workflow configuration editor can be accessed from the [Ontology Manager](../../ontology-manager/overview/index.md) once a Foundry Rules workflow has been [deployed](../deploy-foundry-rules/index.md). The Foundry Rules workflow is tied to a Project and shows as a resource in your Project folder. This controls permissions to the workflow configuration and allows users to rename, move, or delete the workflow.

## Workflow inputs

As explained in the [rule logic inputs](../rule-logic/index.md#inputs) section, the **Inputs** pane of the configuration editor is where workflow owners may add additional inputs for use by rule authors. When adding object inputs, the owner may also select which associated link types they wish to make available.

![Foundry Rules workflow inputs](../../../assets/87d10e35887e576f03070c7c3b1901308378285e64ad98a81c32861fb2cc6d34.webp)

## Workflow outputs

Workflow outputs specify the destination and format for the output of all the Foundry rules in the workflow. Each output corresponds to a different **Foundry dataset** which, when built, will contain the results from all Foundry rules that reference it. Within each output, the name and type of the output columns can be configured. You can also restrict what values the output column [permits and takes as default](../permitted-and-default-output-values/index.md).

![Foundry Rules workflow output](../../../assets/0f45c963da658f74b40846c5eaf7b38901f2ef8c7df08501e62a2affbb76941d.webp)

## Transform configuration

This section contains additional information for configuring the **Transform** that generates the results of the Foundry rules. It includes the location of the rule status dataset as well as any **Spark profiles** applied to the transform. This section represents advanced configuration and can be ignored when first setting up a Foundry Rules workflow.

![Foundry Rules transform configuration](../../../assets/3e4181fb6cad458f116a04f8af142d23e76c4452aaaf9f4fd4456f72e6a7f534.webp)

## Rule execution

The Foundry Rules workflow configuration also generates a transforms pipeline to apply the rules. The transforms pipeline is where the rules take effect; for instance, by creating alerts or categorizing/tagging data. The [Data Lineage](../../data-lineage/overview/index.md) graph below outlines an example Foundry Rules pipeline; the exact structure of a pipeline depends on the use case and may vary significantly based on need and circumstance.

![Data Lineage graph showing the objects backing & writeback datasets, datasets to write rules against, and outputs of rules](../../../assets/2fbccbba89c691c8497cb3c5eb815547b4fed0118ca1d8aeac35a463435ba112.webp)

The pipeline takes the datasets backing the [workflow inputs](#workflow-inputs) together with the writeback dataset of rules and applies these rules to the inputs. It then populates the output datasets specified by the [workflow outputs](#workflow-outputs) with the rows output by the rules.