index.rst

Configure bots

• Out of the box bots does nothing. You have to configure bots for your specific edi requirements.
• Check out different ways to start your own configuration<how-to-configuration>.
• See debug <../debugging> overview for info how to debug while making a configuration.
• Bots also has nice features for configuration change management <../deployment/change-management> (build test sets for you configuration, easier pushing of changes from test to production).

Configuration explained in short

• routes are edi-workflows.
• channels do the communication (from file system, ftp, etc).
• each route hs an inchannel and an outchannel
• Translations rules determine: translate what to what.

Most asked configuration topics

• composite routes <route/composite-routes>
• passthrough route <route/passthrough> (without translation)
• options for outgoing filenames <channel/filenames>
• direct database communication <channel/database>
• partner specific translations <partner/partner-translation>
• code conversion <mapping-scripts/code-conversion>
• view business documents <document-view> instead of edi-files.
• confirmations/acknowledgements <acknowledgements>
• merging and enveloping outgoing edi files <split-merge>
• partner specific syntax <partner/partner-syntax> (especially for x12 and edifact)

how-to-configuration route/index channel/index translation/index mapping-scripts/index grammars/index document-view user-scripting acknowledgements split-merge partner/index charsets