TRAN-IDE objects

Datalinks

A datalink defines a data variable. The common use for a datalink object is to hold a copy of a field object’s data. You can then use the datalink in qualification and filter objects. To use the data variable outside of its module, you must make it “public.” A datalink contains:

• Datalink name

• Module name

• Data type

• Private (static) or public state

Fields

A field object defines a single piece of an input transaction (that is, a record or message) gathered by an acquisition AIM. A field object may contain one or more:

• Data location and length information (required)

• Data type information

• Datalink object references

• Default literal values

• Member-of references

• Qualification object references

• Options

Filters

A filter object manipulates the data in one or more field objects. It can validate, add to, copy, translate, and transform data, or perform any other type of data manipulation you require. A filter object may contain one or more:

• Built-in filter function references

• Custom code references

• Function arguments

• Field object references

• DataLink object references

• Datalink operation codes (for example, <, and so on)

• Table object reference names

• Edit masks

• Options

ODL functions

Object Definition Language (ODL) functions are user-written functions that perform data validation or manipulation. Use ODL functions to perform any type of data manipulation or validation not available through a TRAN-IDE object. See the e-Biz Impact ODL Guide for information about this language. An ODL function is attached to or referenced within:

• Filter objects (custom filter function)

• Production objects (error function)

• Qualification objects (qualification function)

• Rule objects (error function)

Production

A production object defines the requirements and procedures needed to produce a single output transaction from the input transaction. A production object may contain one or more:

• Field object references (required)

• Qualification object references (optional)

• Rule object references (at least one)

• Post-filter object references (optional)

• Comments

Qualifications

A qualification object determines if transaction production should process a transaction through a specific production, rule, or rule component object. A qualification object may contain one or more:

• Field objects or datalink object references (required)

• Literal values

• Operation codes

• Custom code references

• Table object references

• Options

Rules

A rule object contains the components and filters that act on the incoming transaction to produce the output transaction. A rule object may contain one or more:

• Normalized lengths

• Qualification objects

• Rule component objects (one required)

• Post-filter object references

• Options

Rule components

A rule component object defines one or more specific filter objects to process against the transaction, and also defines what piece of data or field object to process. A rule component object may contain one or more:

• Field object references

• Pre-filter object references

• Post-filter object references

• Literal values

• Options

Tables

A table object contains columns of data. You use one of the columns to search for a match to field object data, then place data from one or more of the other columns into the output transaction. A table object may contain one or more:

• Columns of data

• Descriptions

• Options