Runtime

Use this view to configure certain global Ruleset settings. These include selecting data connectors, and may also include null value settings (for Version 1 Rulesets).

Connectors

Connectors are how Clarify joins specific data formats to the transformation engine.

When the source or target data format is either database, XML, spreadsheet, or EDI, Clarify automatically selects the correct connector settings. There is no action required.

It is only when the transformation contains a flat file (as either source or target) that you must select the correct connectors.

For a source flat file, you must choose one of the following:

  • Single Format Delimited
  • Multiple Format Delimited
  • Single Format Fixed Length
  • Multiple Format Fixed Length
  • Multiple Format Delimited, Multiple Transformations
  • Multiple Format Fixed Length, Multiple Transformations
  • Multiple Format Fixed Length, Advanced

For a target flat file, you must choose either delimited or fixed length.

Converter Connectors (source) to dispatch V2 Rulesets from V1 Data Analysis Rulesets (DARS)

Converter Connectors allow you to dispatch Version 2 Rulesets from a Version 1 Data Analysis Ruleset (DARS) for database and flat file. They can accept either Version 1 or Version 2 Storage Nodes as input so that an existing DARS can dispatch both versions of Rulesets. This allows for faster on-boarding and lessens the need to re-create a large Data Analysis Ruleset.

How to use: Take these steps in the Ruleset editor of the Version 2 to be dispatched.

  1. Make sure the Source Schema is selected.
  2. Select the Runtime tab from the Properties view.
  3. Select the Converter option from the Connectors section’s Source drop-down.

(For Database)

(For Flat File)

Change Connectors used within a method (with a StorageNode type parameter)

Now that a Ruleset Method may have multiple StorageNodes and may require multiple Transformation Connectors, the Transformation Connector can be modified per StorageNode. When switching to a Method, the Runtime tab displays each StorageNode parameter for that Method, along with the current Transformation Connector set for that StorageNode

See Changing a Transformation Connector in a Method for more information.

Create Log of Application Batch (Version 2 Rulesets only)

A Log of Application Batch is required for outbound enveloping when not using Data Grouping. When creating a Data Analysis Ruleset (DARS) and routing to an outbound EDI process, select this option in the Ruleset editor to create a Log of Application Batch. If not selected, Clarify will not find any messages for enveloping.

Schema Node Values (Version 1 Rulesets only)

Configure how Rulesets respond to empty nodes (fields/cells/elements) by using several different options. Since these settings are global in nature, only use if you wish to affect every rule in your Ruleset.

Note: This section appears for older Version 1 Rulesets only. It is no longer necessary with the new engine.

Suppress Null Output

Select this check box when you want to prevent your Ruleset from creating null output data (unless explicitly specified in the rules). Depending on the target syntax and the Null Target Action setting (explained below), this property removes the target node from the target document. Other syntaxes and Null Target Action setting combinations are padded with non-null data type default values, essentially preventing null data from being produced.

This check box does not affect EDI data.

Note: See Default Null Values by Syntax for more information.

Extract Numeric Values

Select this check box when want Clarify to scan all data containing mixed characters (alpha and numeric) being passed into a target node, and to remove any non-numeric characters. This table shows examples of how raw data could be scanned and cleaned (non-numeric characters removed).

Raw Data Clean Data
-12.-.345 -12.345
A-12.-.34 -12.34
12-.345 12.345
a1b2c3.45 123.45
abcdefghi null
-12.345 -12.345 (no change)
Note: Selecting this check box affects every rule in the Ruleset.

Null Source Action

This drop-down menu only applies for transformations using Database Schema as source, and either EDI or Delimited Flat File Schemas as target.

The following choices determine how your Ruleset reacts when null source fields are encountered.
  • SkipRuleAndError: The causes an error and stops the transformation.
  • SkipRule: This skip the rule but continues processing of other rules.
  • UseSchemaOrTypeDefaultValue: This uses whatever default value has been set in the Schema's Default Value on Target field. If using a default value, it must be first configured in the Schema editor before this Ruleset option is selected. See Schemas for more information.

Null Target Action

This drop-down menu determines what action your Ruleset takes when receiving a null value for placement in a target node.
  • CreateWithSchemaDefaultValue: This uses whatever default value has been set in the Schema's Default Value on Target field. If using a default value, it must be first configured in the Schema editor before this Ruleset option is selected. This is applied once the rule executes.
  • CreateAllNodes: Creates all blank fields/cells/elements in the target document. This is always used when the target is Database; it cannot be disabled. If your database does not allow nulls, make sure to select the Suppress Null Output check box, and Clarify will use either whitespace or zeroes. For target Fixed-length Flat File; it cannot be disabled. Null values will be the full length of the blank field.
  • DoNothing: This feature is not implemented.

Null Target Action settings do not affect EDI data.

Advanced tab (Version 1 Rulesets only)

Use the Advanced tab to customize several different transformation settings and options. (This tab is no longer necessary with the new engine.)

General

Force Application Analysis: The function is used for Rulesets that were migrated from earlier versions of Clarify (EBI v2 to v3).

If Analysis Rulesets have been imported from earlier EBI versions using the Conversion Manager, this option supports runtime. In this case the Force Application Analysis check box is selected by default, and requires no user action.

Prune Unused Schema Nodes:

When Clarify compiles a Ruleset, it accounts for all Schema nodes, even unused ones. This can create large compilation documents. For example, if you have 1,000 nodes in your Schemas and only use 20 of them in rules, Clarify still documents all 1,000 nodes in a file when compiling. If you do not want the unused nodes documented, select the Prune Unused Schema Nodes check box.

Use Only Internal Attributes:

For Technical Support use only.

XML Source

Not implemented.

XML Target

Not implemented.

Flat File (Source)

Include Empty Records: When unchecked (default), this option skips a source record when that record consists solely of whitespace characters. If you want to account for source Flat File empty records in your target data, select this check box.