Introduction: bots open source translator consists of 2 parts
Bots-engine: the part that does the translations and communication.
The results of translations and communications can be viewed in this interface.
The engine can be run manualy (the 'run' menu) or scheduled.
Bots monitor (GUI); this is where you are now.
Bots-monitor is used to eg:
Set up configuration (what to translate to what, how to communicate, etc.)
Monitor incoming/outgoing edi messages; view results of translations.
Check if edi message have been confimed by the receiver.
Indicate resend of an edi message.
Indicate rereceive of edi message.
Indicate a retry for failed outgoing communication.
Maintain code translations.
Manually start the bots-engine.
Information about menu
Home: default start page and general information.
Last run: view results of last run: report, incoming, outgoing, etc
All runs: view results of all runs: reports, incoming, outgoing, etc
Select: selects the view/results you want to see using criteria.
Select screen can also be reached using 'select'button in other views.
Note that selection citeria are remembered.
Configuration (administrators only): main configuration of the edi setup.
System tasks (superuser only): read plugins, create plugins, maintain users, unlock database, etc.
Run (administrators only): manually start a run of bots-engine:
Run (only new): receive, translate, and send new edi messages.
This is what you normally will do.
Retry user-indicated outgoing communication errors:
outgoing communication can fail (processerror) if eg internet is not reachable, service is out, etc.
The user can indicate to 'retry the communication' for a process error (Process Error-view).
This type of run will handle all user indicated retries of communication errors; no new edi files will be processed.
Run user-indicated retransmits:
a user can indicate to rereceive or resend an edi file (incoming and outgoing views).
This type of run will handle all user indicated resends and rereceives; no new edi files will be processed.
Retry all previous errors:
bots will try to process all edi files that have not been completely processed.
This might be to coarse as ALL previous errors are retried.
If you want more fine-grained control:
For edi files with errors, or stuck files: indicate you want to rereceive specific edi files (and Run user-indicated retransmits).
Remark: if you have not changed the configuration the same error will occur again....of course.
For outgoing communication process errors: indicate you want to retry specific process errors (and Retry user-indicated outgoing communication errors)
User interface tips
You can use tabbed browsing with bots.
In view screens, you can see the contents of an edi file if you click on the file name.
When viewing an edi file, you can go backwards and forwards viewing the steps of processing the file.
View screens often have a star at the beginning of each line; moving over the star will show possible actions.
If you have not been active for a while, bots requires you log in again.
There are 3 levels of user rights: normal users/viewers, administators and superuser. This can be configured in systasks--users.