Legacy Foundry Rules Setup (Taurus)（旧版 Foundry Rules 设置 (Taurus)）¶
:::callout{theme="warning"} 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. :::
Transforms pipeline¶
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.
Workshop application¶
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.
Rule Actions¶
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.
:::callout{theme="neutral"} 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. :::
:::callout{theme="neutral"} 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. :::
中文翻译¶
旧版 Foundry Rules 设置 (Taurus)¶
:::callout{theme="warning"} 在 2022 年 7 月之前，Foundry Rules（原名 Taurus）需要额外配置，并使用略有不同的概念。以下文档涵盖了该版本与较新版本 Foundry Rules 之间的差异。 :::
转换管道 (Transforms pipeline)¶
此前，用户需要自行创建并维护一个运行规则的代码仓库(Code Repository)，而非由 Foundry Rules 自动生成转换管道(transforms pipeline)。
了解更多关于创建和更新此仓库的信息。
Workshop 应用¶
此前，规则输入(rule inputs)需要在 Workshop 应用和转换管道中分别进行配置，而非在工作流配置编辑器(Workflow Configuration Editor)中统一配置。
此外，规则输出(rule outputs)需要在三个位置进行配置：Workshop 应用、转换管道和本体管理器(Ontology Manager)。更多关于旧版规则输出的信息，请参见下文规则操作(Rule Actions)部分。
了解更多关于在 Workshop 应用和转换管道中添加和移除规则输入的信息。
规则操作 (Rule Actions)¶
在工作流输出(workflow outputs)出现之前，输出模式强制是通过 Foundry Actions 实现的。该 Action 的参数代表数据集列，必须映射到逻辑输出的列或用户输入的静态值。可以从转换内部访问规则 Action，以检索指定格式的所有匹配行。当检索指定规则 Action 的结果时，生成的数据集将包含所有使用该 Action 的规则输出的行。这样设计是为了更容易实现所有 Foundry 规则输出的一致性。作为 Foundry Actions，它们必须在本体管理器中进行配置。
了解更多关于配置规则 Actions的信息。
:::callout{theme="neutral"} 虽然规则 Actions 是通过 Foundry Actions 配置的，但 Actions 不会直接在相关对象上执行。目前，其唯一作用是指定输出模式。 :::
:::callout{theme="neutral"} 某些在 2021 年 1 月之前部署的旧版 Foundry Rules（原名 Taurus）需要升级才能使用规则 Actions。除非有特别指示，否则您可能无需执行此操作。
了解更多关于升级以使用规则 Actions的信息。 :::