AutoOrders

Perform the task of automating the process of executing incoming orders in a company with AutoOrders.
This simple yet powerful tool is enhanced with capabilities to automate the process of all incoming orders from customers in a company. The tool serves and manages the process of lining up orders from customers so that the products are processed at the same time. This program supports other features like: the incoming tasks are displayed as "Activities to do" on the terminal of the assignee, it gives the operations manager a clear view of what tasks are running, their past history, users that have been assigned and assignment and finish time; all task assignments are coordinated by "ORDER_MANAGER", all agent actions are displayed in the Developer-Agent Prototypes, and much more.
AutoOrders, this must have application can be freely redesigned for: forms, menu, database schema, agent code, and so on.

The incoming order process automation into a company. Put orders and execute them.The order along with the products goes to the production lines. There every product starts to produced at the same time. The incoming task emerges as "Activities to do" on the terminal of the assignee (user). After the user finishes the job he/she forwards the task, with any number and kind of attached documents to it. The "operations manager" can see at any time what tasks are running, their past history, users that have been assigned and assignment and finish time. All this information is important in order to evaluate every employee's contribution into the company. Every task assignment procedure is coordinated by an intelligent agent, named "ORDER_MANAGER". The agent's action plan (process code) and cooperation with users (production code) are displayed in the Developer-Agent Prototypes. A flowchart is automatically created to show the work-flow of the procedure but also the progress of a running procedure. In order the application to run in multi user mode, using 3 tier configuration, needs an Application Server and Clients . The application can be freely redesigned (forms, menu, database schema, agent code,...) by an application programmer. In order to modify, test and run the agent a special debugger exists. The debugger in the same machine runs debugged not only the action plan of the agent but also the code of the activities that are assigned to users (in other machines). This way the "agent building" becomes a trivial programming task. In the action plan of the agent can be applied wait states, parallel execution split, and joins, or joins, ad hoc parallel splits and subprocess execution.