Features FAQ

Every kosmos AutoPilot Coordinator Agent has an automatic drawing of the status of its action code. Where by red are the finished user activities, by green the activities that are currently worked and by blue the activities to follow. Download Developer and Demo Applications from here. Study the demo applications and you will see why kosmos AutoPilot can do real business programming.

start_action

callwait bpm_assign_job ( "new service request" , __activation_user , "" , 0)

callwait bpm_assign_job ( "service appointment" , "" , "GATE SECURITY" , app_date_num , serv_id )

callwait bpm_assign_job ( "service estimation" , "" , "CHIEF MECHANIC" , 0 , serv_id )

split_in_branch

callwait bpm_assign_job ( "collect parts" , "" , "WAREHOUSE" , 0 , serv_id )

and_branch

callwait bpm_assign_job ( "disassemble" , disas_mechanic , "" , 0 , serv_id )

join_branches

callwait bpm_assign_job ( "reassemble" , reass_mechanic , "" , 0 , serv_id )

and_branch

callwait bpm_assign_job ( "host customer" , "" , "HOSTESS" , 0 , serv_id )

join_branches

callwait bpm_assign_job ( "payment and goodbye" , "" , "OFFICE" , 0 , serv_id )

end_action

clip0051

Because for a Business Application Developer like you, the need of a tool that can follow business logic without any compromise is out of the question. And this without sacrificing speed of development and easy of support.

Because you can code directly any business procedure as soon as you hear them from your customer. See how.

Because your customer's business procedure will followed by the users/employees as you coded. See how.

Because you can provide to your customer a business monitoring system for all running procedures. See how.

The speed in development comes from tow directions. The first is the type of development cycle and the second the easy of programming business procedures (few lines of code for a huge result). Now for the first direction, the development cycle:

There is no "design-compile-linking-running" in the development cycle in kosmos AutoPilot. The programmer enters the application (as a user) and by right clicking the mouse "designs-scripts-tests" every resource (form, report, menu, scripts, database and agents). The application is always in running mode except that the programmer can select any resource and "create-redesign" it. This can be happen even on the customer's site for a delivered application (test-develop using live data). Download the Demo Applications and test here.

When we code business procedures the kosmos AutoPilot is unbeatable (not to mention that other RADs simply cannot program business procedures at all!). See here how a business procedure becomes a coordinator agent.

All the resources of a kosmos AutoPilot appilication, forms, reports, menus and scripts are small files (out of the delivered executable). If for example a customer asks for a new report, then the procedure of supporting is the following: The application programmer modifies the menu (in order to add the new report). Builds the new report. Now the two files (modified "menu" and new "report") are emailed to the customer. That's all. Another interesting feature in supporting is that by replacing the delivered kosmos.exe by the "design enabled" kosmos.exe the supporter can design the delivered application as he was in the office.

It is a RAD tool for the Business Application Developer, that has unique features like Business Process Management, Business Activity Monitoring, Business Rules Management System, Software Agents, Document Management, 3 Tier architecture over Internet, Resources out of the executable and some more conventional like Form Designer, Report Builder, Code scripting and more..

Because you have to use only one tool to deliver full of business logic applications. Otherwise you need more than one tool (a conventional RAD, a BPM, BAM and document management and all of the labor to make them cooperate). Finally the "out of the box" feature of 3 Tier architecture. The choice is obvious!

Yes. Software agents can be of three different types (They differentiate accordingly to the AutoScript code that have in their "action section"). There are the coordinator agents, the planners and the experts. The coordinator agents execute on the server and partly on the clients. Their job is to coordinate any business procedure of any depth and any number of engaged employees. The planners are agents that execute on the server. Their job is to apply business activity monitoring. They can alarm for business critical situations and start coordinators. The experts are agents that apply business rules every time they called (run on the server but can called from the clients also). More on software agents here.

No programming at all. All applications that build in kosmos AutoPilot have inherently the capability to store and attach any kind of document (file) that the operating system (windows) supports. The documents are stored compressed into the server computer and can be related/attached to any record/form of the application. That's simple! Check it in demo applications.

No programming at all. All applications that build in kosmos AutoPilot have inherently the 3 Tier architecture.

No there is no executable producing. In kosmos AutoPilot there is only one executable, the "kosmos.exe". This executable is the program that acts both as "Server Application" and "Client Application", but not only. "kosmos.exe" runs also as a Developer's tool in order to "develop" the final application for the customer.

Which is the executable that uses the developer in order to build an application?

Which is the executable that runs on server computer, in a delivered application?

Which is the executable that runs on client computers, in a delivered application?

Yes. Evey kosmos AutoPilot application works with a specified database. Specific information is stored in about 30 "system tables" (with names started as "AU_*"). Currently are supported MS-Access and MS-SQL Server. Oracle is coming soon (using the same "kosmos.exe"!).

You can select from the "Downloads" page the kosmos AutoPilot Developer. After downloading you install it against the specified database. Then automatically "system tables" are created into the database (backup it first!). The database schema with any relations between tables is extracted and stored to the "system tables". A browsing form and an editing form (with searchable drop down lists for the foreign keys) are created also for each table of the database. A typical report also is created for each table of the database. Finally a menu is created that calls all of the above forms and reports. The next step is to login into the "instantly created application" by using "admin" as a user name with a blank password.

Now you are at a good starting point in order to further develop the "instantly build application". You have at this point already understood that the application is also and developing tool for that application!

All browsers, forms, (*.FM) reports (*.RT), menus (*.MN) and database schema (*.DB) are small files that remain on the central resource directory. These are used in the server’s user interface or copied as the user interface of the client applications.

Where do forms, reports, menus and scripts, that the developer designs and writes, are stored?

All those (forms, reports,...) are named resources and they are stored as small files into the same folder as "kosmos.exe". The clear result for that is enhancement of teamwork programming and very easy customer support (the new report or the faulty form can be e-mailed to the customer!). To use a parallelism the "kosmos.exe" and its resources from one side and a web-browser with HTML files from the other.