A Process Server is a collection of Web services that can create and manage Business Processes and render as a Software Application. Process Server is the next logical step to the Database Server in Technology Evolution. A database server manages data that is represented as table structures. Similarly the Process Server manages business processes that are represented as process structures.

A Process structure is a set of related database tables along with business rules. Business rules seldom make sense without data. Hence, business rules are tightly bound to a collection of data elements that are persisted into one or more related database tables. Every business entity in a software application can be considered as a process structure.

A Business process is created by inter-connecting the different process structures. The connection between process structures are achieved by mapping the elements in one process structure to another. The process structures can be connected with different kinds of maps based on business need.

The basic version of Axpert ^TM consists of two major components

• Axpert ^TM process server

• Axpert ^TM STEM (windows desktop application)

Axpert ^TM STEM (Structure Execution and Management) is used to define process structures. The defined process structures are rendered by the Axpert ^TM Process Server as an application.

On creating a process structure, Axpert ^TM stem will store the structure definition into database in XML format. Further, it creates the required tables in the database to store user data.

A Process Structure will consists of

The data elements are grouped into data containers. Every container is linked to a database table. Hence, when the structure is created, the tables attached with each data container are created in the database and the fields associated with each container are created as fields in that table. If a structure consists of more than one table then all the tables are related.

Each data element can be associated with an expression. The expression can be based on the data elements in the structure. Axpert ^TM provides a list of common functions that are needed for the building comprehensive structures. In case more functions are needed, these can be written in dot net as web services and attached to the structure. Alternatively, SQL functions can be written and used in SQL statements that can be attached with the data elements.

SQL statements to fetch and populate data into structure

SQL statements can be attached with every data element. The SQL result can be automatically populated into the data element or the user can be allowed to choose from the SQL result.

Validation rules

Just as expressions can be set to compute values into data elements, there can be validation expressions that will validate the value in a data element. The result of any validation expression should be ‘T’ if the value is valid or ‘F’ in case of invalid.

Actions

An action is a sequence of tasks that can be performed within if-else constructs. Process flows are created as actions. An action can be associated with an event, attached to a button or may be attached to the Axpert ^TM scheduler.

Maps to other structures

Maps are used to populate data from one structure to another. As part of a map the data elements in the source structure will be mapped to data element in the target. One-to-one, one-to-many or many-to-many maps can be defined between structures. The flow can be controlled based on rules.

The Process server will read a process structure (created by the STEM) and renders a page. The page provides a user interface to enter & submit data into the structure. The data that is submitted is validated and stored into associated database tables. The various actions and maps associated with the structure will be executed by the server. The stem consists of a full fledged form designer that can be used create the page design.

The Process server can do any or a combination of the following task

• Render standard GUI along with navigations

• Manage CRUD operations

• Do Data conversion to various formats

• Provide connections to productivity tools like word, outlook, excel

• Manage Work flow

• Handle reporting

• Do scheduled activities

• Exchange data based on maps

Future versions of the server will be enhanced to provide more such native tasks.

Every task that the process server performs on a process structure is available as web services. For example saving data to any structure is available as service, sending structure data as email is available as web service, converting structure data to PDF is available as another web service. Hence, all functionality in the end application that is rendered by the process server is available as web services. Hence, the level of inter-operability is the highest.

Implementation Business Rules

Computations

The simple rules to compute values of data elements are defined as mathematical expressions and attached to them. The expressions are based on the data elements within the structure. If the expression needs data from other structures, those are brought into data elements in this structure using SQL statements.

Axpert ^TM provides a set of functions that are mostly required to build enterprise wide applications. However, if there is a need for more functions, SQL functions can be written and called through SQL statements or Web services can be written and attached.

Very complex computations can be achieved by writing a set of expressions that are to be executed in a sequence.

Validations

Data that is submitted to the structures need to be validated. Mathematical expressions that return true or false are attached to data elements. Hence, the value submitted to every data element is validated using the given expression.

Database processes

Many of the very complex and high volume processes can be achieved through a stream of SQL statements inter sparse with mathematical expressions. These are attached to the structure as actions that can be invoked based on events or button clicks.

For example a payroll process, that consists of various rules that are persisted to tables need to be applied to employees or employee groups. These can be achieved by writing SQL streams.

Algorithms

There may be need for doing iterative loops and complex programming logic for achieving some tasks. For example Material Requirement Planning algorithm, traveling salesman algorithm, capacity planning algorithms and the likes are complex piece of programs that cannot be achieved just by a sequence of expressions. Some of the algorithms like MRP are available in the process server. The future versions of the process server will consist of all the common algorithms. However, at any point of time a complex algorithm is needed that is not part of the process server, those can be achieved by writing database SQL functions or attaching them as web services to the process server.

Axpert ^TM Features

Reporting

Tabular reports are mostly SQL results presented in convenient formats. These are defined as information views (IViews) as part of the process structures. The IViews are read by the process server and presented in a tabular format. The process server will manage control breaks, filtering, sorting and grouping of the SQL result. The IViews are dropped into pages and navigation from the page is provided by way of hyper links.

Hence, reporting becomes a simple on the fly job.

The Axpert ^TM STEM provides a PDF form designer that can be used to create any free form report based on one or more SQL results. These are also stored as part of the structures. The process server will read these formats and render free form reports.

User Roles

User roles are created and access rights are set to structures. Access to different structures can be allowed or denied. Further, access to the transaction data in a structure can also be defined. This will help in implementing record level access to records. The access to every component in a form can be controlled for a role based on conditions. This will enable building complex forms that need to be displayed differently for different roles.

User groups are created and one or more roles are assigned. Users are created and attached to user groups. The users from an active directory or from a LDAP server can also be assigned to different user groups created in Axpert ^TM. This will enable single sign on. (LDAP and active directory connectivity under development)

Axpert Scheduler

Actions that are attached to different structures can be assigned to the scheduler. These actions will be executed based on the time interval. There can also be business rules based on the (structure data elements) to execute actions. This will enable defining exceptional reporting, escalations and automated work flow.

Axpert ^TM Exchange Server

This server will handle data exchange between different applications. The first version of this server will support data exchange in XML format through an FTP server. This can be used to exchange data with external vendors/partners. An XML map is written to map the data in the XML to the data elements in a structure. Similar maps can be created to convert SQL result to a user provided XML file based on a map.

Axpert ^TM Synchronizer

This is a set of services that will handle data exchange between two Axpert process servers. This will enable implementation of distributed data architecture (store and forward smart client). This is achieved by submitting the structures to the synchronizer that need to be synchronized between servers. The synchronizer will automatically detect the new/modified data in the structures and send to the other servers it is intended for. The server identifications of the different server to which the data needs to flow can be made part of the structure in data elements.