You can control validation by setting properties presented by the Validation tab on the Compute, Mapping, and MQInput nodes.
Content And Value indicates that you want to perform content checks (such as Content Validation and Composition) and value checks (such as value data type, null permitted, length, range, enumeration).
Exception throws an exception on the first validation failure. The failure is logged in the user trace if you have asked for user tracing of the message flow, and validation stops. This default setting is most useful after you have completed debugging your message flow and application.
User Trace writes all validation failures to the user trace, even if you have not asked for user tracing of the message flow.
Local Error Log writes all validation failures to the error log (for example, the Event Log on Windows).
In both the User Trace and Local Error Log cases, validation continues. These settings are useful when you first set the Validate property to Content And Value, so that you see all validation failures, not just the first.
Immediate validates the entire message, although any unresolved subsets resulting from the use of Composition Choice or Message are not validated until they are resolved.
Complete validates the entire message.
Deferred validates each field when it is parsed. Partial parsing might cause this to be late in the message flow, or never.
The Timing property is available only on the MQInput node.
Include All Value Constraints specifies these value constraint checks:
See Simple type logical value constraints for a description of these value constraints.
Related concepts
Message flows
Related tasks
Validating messages
Designing a message flow
Creating a message flow
Defining message flow content
Related reference
Built-in nodes
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac18870_ |