User Guide : Designing and Executing Processes : Process Steps and Associated Components : Validator Step
 
Share this page             
Validator Step
Validator steps allow you to validate a document against a supplied schema. These steps check data at a structural level, such as the loop repeat count, segment information, minimum and maximum field length, and field values. The validators do not provide conditional validation or validate the data itself.
Before creating a process using the Execute action, create and initialize a DJMessage process variable. Load the file to validate into the body of the new DJMessage. See DJMessage Object Type for more information.
Validator Step Properties
After adding a Validator Step from the Palette to the canvas, you can double-click the step on the canvas and specify the following step properties in the Properties tab displayed at the bottom.
Setting
Description
Name
Unique name for the step.
Description
Description of the step (optional).
Enabled
Select this option to enable the step for execution. If it is not enabled, then the step on the canvas is greyed-out.
This option is useful when troubleshooting a process, especially when there are numerous steps in the process.
Error Handling
Select any of the following:
Abort Process - All the steps after the current step are skipped or the entire process is stopped (depending on how you have set the error logging options) if this step stops due to an error.
Ignore Error - The remaining steps in the current process are executed even if this step stops due to an error. This is selected by default.
Select Validator
Select a Validator instance. These instances are displayed when you add a Validator message component in the Configuration tab. For more information, see Adding Message Components in Configuring Processes.
Action
Select the action for the Validator instance.
Parameters
Parameters for the selected action. Specify the values for the parameters.
Properties
Properties for the selected action. Specify the values for the properties.
Note:  The Actions, Parameters, and Properties are specific to the component type. For information about this, based on the component instance selected in the Select Validator drop-down list, see the component type in Validator Step Components.
Validator Step Components
XML (DTD) Validator
XML Schema Validator
EDI 999 Validator
HL7 Message Structure Validator
TA1 Validator
XML (DTD) Validator
The XML (DTD) Validator validates the HIPAA document against any DTD that is declared inside the XML document. If DTD is not declared, then only a syntax check is performed.
XML (DTD) Validator Properties
This validator component does not have any instance properties that you can specify when you create an instance of this validator component in the Configuration tab > Message Components section
Supported Actions
 
Action
Description
Execute
Validates a XML document against a DTD.
Supported Action Parameters
Action
Parameter
Description
SourceMessage
Message
(Required) XML input source message name.
Target Message
Message
(Required) Target message name. Output is in XML format.
Supported Action Properties
There are no supported action properties.
XML Schema Validator
The XML Schema Validator checks the structure of an XML file against a supplied XSD (XML schema document) file.
XML Schema Validator Properties
You can specify the following properties when you create an instance of this validator component in the Configuration tab > Message Components section.
Property Name
Description
W3C XML Schema File
Path or URI to the XSD file.
Supported Actions
Action
Description
Execute
Validates a document against a schema. The output is in XML format.
Supported Action Parameters
Action
Parameter
Description
SourceMessage
Message
Required. XML input source message name.
TargetMessage
Message
Required. Target message name. Output is in XML format.
Supported Action Properties
There are no supported action properties.
Errors
The validator supports the following error conditions.
Error Code
Error Name
Description
46
LICENSING
A valid product license is not found.
50
UNSPECIFIED
An unknown error occurred while loading the validator.
4
READER
The XML is not well formed and cannot be parsed.