Description

Displays a system-generated ID to uniquely identify the validation.

Displays a value that determines the order in which the validation runs.

Displays the type of validation rule for the interface. Options are:

• External Process
• Stored Procedure
• View

Displays why the validation is needed. Options are:

• Validation – Interface is not run if the view returns records.
• Requirement – If the view returns a value, then the validation has failed.

Displays when the validation runs in relation to the event. Options are:

• Pre – Validation runs before the event runs.
• Post – Validation runs after the event runs. This option is typically used to determine if an event has run to completion.

Displays what happens next if the event fails the validation. Options are:

• Abort – Unexpected condition. If the validation fails, the interface is turned off, and workflow emails are sent to the business and technical roles.
• Consider Complete – Expected condition. The interface does not retry, the event is considered complete and the next event runs.
• Retry – Expected condition. The interface retries this event/validation until there are no more event validation failures.

Displays the view name as selected from the Validation View, Validation Procedure or Validation Plugin (depending on the Validation Type) on the Vertical View.

Displays description of the validation entered on the Vertical View

If checked, the validation has been tested and is ready to be run.

If unchecked, the validation does not run when the interface is either manually run or set to run on a schedule.

It is checked by default.

If the External Page is Izzy.IO.CheckForFile, this field displays the file operation that is passed to the FileInterator event.

If the External Page is any other value, this field is blank.

Description

Displays a system-generated ID to uniquely identify the validation.

Displays a value that determines the order in which the validation runs.

Displays the type of validation rule for the interface. Options are:

• External Process
• Stored Procedure
• View

Displays why the validation is needed. Options are:

• Validation – Interface is not run if the view returns records.
• Requirement – If the view returns a value, then the validation has failed.

Displays when the validation runs in relation to the event. Options are:

• Pre – Validation runs before the event runs.
• Post – Validation runs after the event runs. This option is typically used to determine if an event has run to completion.

Displays what happens next if the event fails the validation. Options are:

• Abort – Unexpected condition. If the validation fails, the interface is turned off, and workflow emails are sent to the business and technical roles.
• Consider Complete – Expected condition. The interface does not retry, the event is considered complete and the next event runs.
• Retry – Expected condition. The interface retries this event/validation until there are no more event validation failures.

Displays the plugin name assigned to the external process validation. The selection populates the NAME field on the Horizontal View.

NOTE: This field only displays for External Process validations.

Displays the registered validation view. Only views ending in “Val” display, as defined by the Validation Filter field on theParameters page. The selection populates the NAME field on the Horizontal View.

NOTE: This field only displays for Stored Procedure validations.

Displays the registered validation view. The selection populates the NAME field on the Horizontal View.

NOTE: This field only displays for View validations.

Displays a description of the validation. Only views ending in “Val” display, as defined by the Validation Filter field on the Parameters page.

NOTE: This field only displays for View validations.

If checked, the validation has been tested and is ready to be run.

If unchecked, the validation does not run when the interface is either manually run or set to run on a schedule.

It is checked by default.