Table of Contents

Search

  1. Preface
  2. Introduction to Rule Specifications
  3. Rule Specification Configuration
  4. Rule Set Configuration
  5. Rule Statement Configuration
  6. Common Types of Rule Statements
  7. Test and Validation Operations

Rule Specification Guide

Rule Specification Guide

Inputs

Inputs

An input describes a column of data that a rule statement can analyze. An input represents a column in a data set, or an input represents the output from another rule set in the rule specification.
Use the
Manage Global Inputs
dialog box to define an input.
When you define an input, specify the following properties:
  • The data type of the data that the input represents. Create an input with a date/time, float, integer, or string data type.
    You can specify an integer data type for numbers in the range -2147483648 through 2147483647. To read numbers that are outside the integer range, use the float data type.
  • The maximum number of characters that a value in the column can contain.
You can optionally enter a text description of the input.
An input does not store information about the business data, such as the name of a column, table, or database. The Developer tool user adds the mapplet or the rule specification to a mapping and connects the mapping inputs to the business data. You advise the developer about the columns to connect. The developer can connect an input to any column that matches the properties that you define.
When you create a child rule set, the output from the rule set becomes an input to the parent rule set. You must use the input in a rule statement in the parent rule set. When you create an input in the
Manage Global Inputs
dialog box, you can optionally add the input to a rule statement. To view the inputs that a rule set uses, select the rule set in the workspace.

0 COMMENTS

We’d like to hear from you!