Setting the rule schemas - Cloud - 8.0

Business rules

Version
Cloud
8.0
Language
English
Product
Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Real-Time Big Data Platform
Module
Talend Studio
Content
Data Governance > Third-party systems > Processing components (Integration) > Business rules components
Data Quality and Preparation > Third-party systems > Processing components (Integration) > Business rules components
Design and Development > Third-party systems > Processing components (Integration) > Business rules components

Procedure

  1. In the design workspace, double-click tRules to display its Basic settings view and define the component properties.
  2. In the Property type list, select Repository if you have stored the file that holds the business rules in the Metadata > Rules management node of the Repository tree view. If not, select Built-in and browse to the Drools file.

    For more information on how to create and store business rules, see Talend Studio User Guide.

  3. In the Outputs table, click the plus button to add two rows that represent two different output flows, each using one of the two business rules defined in the Drools file.
  4. Click in the first row of the Schema column to display a [...] button. Click the button to open a dialog box and set a name for the output schema.
  5. Enter the exact name of the first rule as it is written in the Drools file, RuleAGE in this example, and then click OK.
  6. Define your output schema in the dialog box that opens. In this example, we want to recuperate the input schema. Click OK to close the dialog box.
  7. Do the same in the second line of the Schema column.

    Enter the exact name of the second rule as it is written in the Drools file RuleREGION to have it as the name of the second output schema, and then recuperate the input schema in the open dialog box.

    You will have an error message when trying to execute the Job if the name of the output schemas in your Job do not match the exact names of the rules in the Drools file.