Prior to July 2022, Foundry Rules (previously known as Taurus) required additional configuration and used slightly different concepts. The following documentation covers the differences between this and newer versions of Foundry Rules.
Previously, instead of Foundry Rules generating the transforms pipeline automatically, users were required to create and maintain a Code Repository that ran the rules.
Learn more about creating and updating this repository.
Instead of the rule inputs being configured in the Workflow Configuration Editor, they were previously required to be configured in both the Workshop application and the transforms pipeline.
Additionally, rule outputs were configured in three locations: the Workshop application, the transforms pipeline, and the Ontology Manager. Learn more about legacy rule outputs in the Rule Actions section below.
Learn more about adding and removing rule inputs in the Workshop application and the transforms pipeline.
Before workflow outputs, output schema enforcement was achieved with Foundry Actions. The parameters of the Action represent dataset columns and must be mapped to either columns outputted by the logic or static values inputted by the user. The rule Action can be accessed from within the transform to retrieve all matching rows in the specified format. When retrieving the results for a specified rule Action, the dataset produced will contain the rows output by all rules which use that Action. This is designed to make it easier to achieve consistency in the output of all Foundry rules. Being Foundry Actions, they must be configured within the Ontology Manager.
Learn more about configuring rule Actions.
While rule Actions are configured with Foundry Actions, Actions are not executed directly on top of the relevant objects. Currently, the only effect is to specify the output schema.
Some legacy versions of Foundry Rules (previously known as Taurus) deployed prior to January 2021, need to upgrade in order to use rule Actions. Unless you've been specifically directed to, you likely do not need to do this.
Learn more about upgrading to use rule Actions.