- Welcome
- Introducing Babelway B2B Integration
- Starting with Babelway
- Managing Account Environments
- Managing Channels
- The Catalogue
- Tracking Messages
- Managing Alerts
- Managing Your Account
- Best Practices
- Channels
- List of Channels
- View Change Log
- General
- Gateway In
- Message In
- Transformation
- Message Out
- Gateway Out
- Email Gateway Out
- Ftp Client Gateway Out
- SFTP Client Gateway Out
- Ftp Server Gateway Out
- AS2 Gateway
- Http Client Out Gateway
- Web Gateway
- Generic Gateway
- Internal Gateway Out
- Null Gateway
- OFTP Server Gateway out
- OFTP client Gateway out
- Http Out Gateway
- SOAP Gateway
- Soap Client Out Gateway
- X.400 Gateway out
- Aggregator Gateway Out
- Email Gateway Out
- Email Notifications
- Routing
- Testing
- List of Channels
- Building a Channel
- The Catalogue
- Tracking Messages
- Alerts
- Account Management
- Rest API
- Receive Orders From
- Receive Orders from Colruyt
- Receive Orders from Carrefour
- Receive Orders from Brico
- Receive Orders from Castorama
- Receive Orders from Cora BE
- Receive Orders from Delfood
- Receive Orders from Delhaize
- Receive Orders from DEliXL
- Receive Orders from Intergamma
- Receive Orders from Intermarche
- Receive Orders from JavaFresh
- Receive Orders from Makro
- Receive Orders from Match
- Receive Orders from Carrefour France
- Receive Orders from Colruyt
- Integrate Orders with
- Integration with Tradeshift
- Integration with Exact Online or Exact Globe
- Channel:SAP Idoc XML Order05 w/ Http client out
- System Metadata
- ODETTE Messages List
- External References
See: Managing Channels - Message Edit Functions
In Babelway interface, it is possible to set up validations at message definition level.
You can set up validation rules for incoming and/or outgoing messages. These validations will be performed at runtime on messages.
To add validation rules, right click on a node in message definition window and select Add Validations... submenu. There are 3 basic validation rules that you can set up directly. In addition, you can also define your own rules in Xpath language.
Mandatory
is used to check that the selected (value or structural) node is always present in the message.
Max Length
defines a maximum length for the node value.
Min Length
defines a minimum length for the node value.
Custom
enables you to define your own Xpath validation rule.
Several validation rules may be applied to a same node. For example, using together a Max Length and a Min Length rule makes it easy to check that a node value has a specific length.
Once a validation rule has been added to a field, it will appears under the
Validations
section of message node. It can be removed by right-clicking on the validation rule and selecting the
Delete
command.
Example of Xpath validation rule:
string-length()>4
matches(.,"\d+") to validate if this field is only numeric
Example of cross field validation rule:
For XML like this
<item> <price>456</price> <tax>123</tax> </item>
You can write Cross field validation like
price > tax
If a validation rule is not met in a message, this message will not be further processed in the channel and an error will be raised.
If you are using XSD to define your incoming or outgoing message, all rules defined in XSD file will be validated at runtime even if you do not add specific validation rules at message level.
During xslt transformation, all data is seen as text string and therefore no specific validation is performed on data type at that stage.
Validation uses static values to identify the node to validate. If, after a mapping, a static value is overwritten, the validation my not be able to apply anymore, and may not validate all nodes.
Babel Academy
Community Forum
Support



Prev
Up
Reference Manual