Bpm Technical

Accpol BPM Detailed System Description

January 2005

From Polymorph Technologies Pte. Ltd.

Eform Technical Documentation January 2005

1 Introduction The E-form Application will be a combination of several different subsystems, which will allow browser based forms to be generated, placed on the intranet, with the results stored in a database, which can then be queried by an administrator and form users. This Document covers five main sub-systems of ACCPOL BPM Application, Requirement specification: 1. ACCPOL BPM Designer ( Designer & workflow) 2. ACCPOL BPM Application(ACCPOL BPM Handler ) 3. ACCPOL BPM Admin 4. Scheduler System 5. Archival System

1.1 ACCPOL BPM Designer: The ACCPOL BPM Designer Module helps the user to design, develop and deploy the e-form application:

1.2 Design Development ACCPOL BPM ƒ ƒ ƒ

Design Report Form Templates Manage Designer Configuration Manage EAI Configuration

1.3 ACCPOL BPM Admin: This is the Admin module, manages ƒ ƒ ƒ ƒ ƒ ƒ ƒ

User Management Form Access Management Application Management Log Management Form Management (ACCPOL BPM & Reports ) Scheduler Management Archival Management

1.4 Scheduler System: The scheduler programs will be running in the Database and Application server for the following purposes. ƒ ƒ ƒ ƒ ƒ

Archival of old/expired data. Activation or Deactivation of the forms. ACCPOL BPM Processing expiry handling (Covering Officer) Reminder Messages and Notification Synchronization of Master Data from External source

2

Eform Technical Documentation January 2005

2 About BPM Web Based Form [Electronic Form – Dynamically generated from configuration]

2.1 ACCPOL BPM Data BPM Configuration

BPM Instance Data

BPM Properties

Eform

BPM Data ACCPOL Comments

BPM Layout

BPM

Eform History

BPM Workflow (Control Data) Eform Access Control Eform Access Control

Eform Role Subscription

3 ACCPOL BPM Designer ACCPOL BPM designer provides following helps the Designer to design and manage the form/reports. Also it allows the designer to manage the design related configurations.

3.1 Design wizard Wizard will help the User create and modify the ACCPOL BPM Form Properties Select Template

Form Layout

Form Resource Table Management

Form State Management

Form Generate XML File

3

Eform Technical Documentation January 2005

Designer Wizard Screens: ƒ ƒ ƒ ƒ

Form Properties: Set the Form Properties and General Settings Form Layout : HTML Layout Management Resource Table Management: Store form Data Form State Management: Define workflow and Routing Information ƒ State Management ƒ State Properties ƒ Server Validation ƒ Sub forms Settings ƒ Data Mapping ƒ State Task

The ACCPOL BPM Administrator/Designer cannot edit an existing ACTIVE form. But He can create new version and modify it. Using Form Designer wizard user can Design and Edit forms. 3.1.1 Data Mappings ƒ ƒ ƒ ƒ ƒ ƒ ƒ

Data Mapping Name: User Defined Unique Map Name Map Between Form Field - Database Field Required Information Table Names Form Field Names Table Field Names User Can Define Criteria [Only for Query, Update & Delete]

3.1.2 Database Task: ƒ ƒ ƒ

Insert/Update Data - Require DB Map/Criteria Query - Require DB Map & Criteria Delete Require Criteria

4 Routing & work Flow Settings 4.1 Workflow processes The workflow technology is emerging as an appropriate platform for the automated co-ordination of business connectivity. The documents represent the primary medium of business communication. Almost all kinds of business activities have some associated documents. Most of the information modeling techniques includes graphical representation that enhances the understanding of the models. A workflow specification could also be represented using graphical objects. The workflow specifications model proposed in this paper includes four types of objects: task, condition, synchronizer and flow. The flows are used to link the first three types of objects together to build workflow specifications. Figure 1 shows the graphical representation of these objects in our model.

4

Eform Technical Documentation January 2005

Task

Condition

Synchronizer

Flow

4.1.1 Task - (Role) A task is the primary workflow-modelling object and represents the work to be one to achieve some given objectives. The aim of workflow modelling is to capture the co-ordination requirements for performing a set of tasks for a given business process. Each Task will have Unique Role/Performers. (TASK:ROLE) 4.1.2 Condition A condition is applied to represent alternative paths in workflow specification depending on an externally provided condition value. 4.1.3 Synchroniser At certain points in workflow, it is essential to wait for the completion of more than one execution path before proceeding ahead. A synchronizer is used for this purpose and it simply waits until all the incoming flows have been activated. 4.1.4 Flow A flow defines the connection between any two objects, other than flows, in the workflow. It shows the flow of information as control and data parameters from one object to another. By connecting workflow objects with the help of flows, we build directed graphs of workflow specifications where flows represent edges; and tasks, conditions, and synchronisers represent vertices.

Alternative The alternative construct is used to model two or more mutually exclusive Alternative paths in a workflow. It is constructed by attaching two or more outgoing flows to a condition object. The condition is a primitive object in our model and depends on external parameters. It takes a set of control and data parameters and a condition value from the preceding task at run time. On the basis of the condition value, it selects one of the alternative workflow execution paths for a given instance of the business process by activating one of its outgoing flows. It is essential in our model that the condition is exclusive and complete. The exclusive characteristic ensures that only one of the alternative paths is selected. The complete characteristic guarantees that, in all instances of the workflow that invoke the condition, one of the alternatives shall be selected. Exclusive Join The exclusive join construct is opposite to the alternative construct. It is applied to join two or more mutually exclusive alternative paths into one path. It is constructed by attaching two or more incoming flows to a task or condition object. Start / Stop

5

Eform Technical Documentation January 2005

The initial and final tasks are used to represent the start and stop constructs of workflow specifications. All workflow have at least one initial task and one final task. ƒ

Work is performed on FORM. An object could represent any entity of interest. In postgraduate admission workflow, the admission application form represents a workflow object.

ƒ

Tasks specify the work to be done. The work specified by tasks is generally performed on ACCPOL BPM & Database Object or on the basis of information contained in objects. Characteristics. Some of them apply only to document workflow.

ƒ

Performers/Role carry out the work. Tasks cannot perform the work themselves. They need the services of performers. For example, a Manager who reviews the form is the performer.

ƒ

Constraints control correct execution of the work. Tasks specify what to do and performers carry out that work. The constraints ensure that the work is performed correctly. For example, one of the constraints of the Manager review of application form task could be to complete the review within two working days after receiving the application form.

4.2 Work Flow Building Blocks

Performer/Role

ACCPOL BPM Perform

Control

Manipulate Tasks Manipulate

Constraints Control

For each business process, we could identify the above four components. Generally, the document workflow has following high level properties for these building blocks: ƒ ƒ ƒ ƒ

Objects: Primarily sets of documents. Tasks: Addition to or modification of the contents of documents; decisions and actions based on the information in documents. Performers/Role: mainly humans. Constraints: mostly human-oriented.

Form designer handles Objects, Tasks & Performers & Role. The Form Access Management controls the access & constraints and covering officer for routing purpose.

6

Eform Technical Documentation January 2005

4.3 ACCPOL BPM Inbox ACCPOL BPM Inbox is similar to Outlook Inbox, All incoming ACCPOL BPMs are posted on the Inbox. Inbox provide following functionality: ƒ ƒ ƒ

Open & View ACCPOL BPM instance Process ACCPOL BPM Instance through ACCPOL BPM Handler Search Inbox Inbox has a search and find function in built, using which users can search all messages part of their inbox messages based on the following conditions;

Shared Inbox The Shared Inbox allows one or more user view all incoming form instances for that particular shared inbox. But only one user can take the ownership of the form, by accepting the form. Once user accepts the form for processing, other user will be notified through shared inbox. User Preference Using the user preference form user can set following options: ƒ ƒ ƒ ƒ ƒ

Notify before Processing Expires Delegate form (User List) Other User Preference Settings Default form priority Out Office setting

4.4 Form Handler The form handler component manages following task: ƒ ƒ ƒ Also it manages

Workflow Task Execution Access control the Form control data, Transaction data and Presentation data.

XML File stores Control Data Information

Form

Database (Resource Table) – Transaction Data Presentation data are stored in HTML file

XML File stores Tracking & Comment information

7

Eform Technical Documentation January 2005

4.4.1 Form Common Task: [toolbox Task] ƒ ƒ ƒ ƒ ƒ ƒ ƒ ƒ ƒ ƒ ƒ ƒ

Add and View Comments Track and View History (If Enabled) Save Draft – ( Draft Folder ) Close – Return to previous screen Feedback (If Enabled) Hold Form – Hold the form Print Option Attach Files & Attach Sub Forms Change Priority View History View Route Delegate form instance

4.4.2 Feedback Loop User can forward the form instance to feedback purpose without changing the state. The form designer only specifies the feedback group on form level basis. Designer can configure Following Feedback groups: ƒ ƒ ƒ ƒ

Organization User Group Department All

4.4.3 Hold Form Using this option user can hold the form instance until Maximum Processing Period expires. The Admin can set the following parameters for each state: ƒ ƒ

Normal Processing Period: ( Processing time without Hold option) Maximum Processing Period: ( Processing time with Hold option)

When form-processing period expires, the form is pass to the covering officer (If available). By holding the form user can extend the processing time. Also designer can set the HOLD TIME OVERWRITE OPTION for form level. If this option is configured, the Administrator can extend the hold time for a form instance. 4.4.4 Form Recall Form call be recalled any time as long as the form is not processed not processed by the next stage. 4.4.5

Attach Files & Sub Forms

The Designer can configure which state user can attach files/Sub Forms for Form or state based. Also designer can set the file type or Sub form Name/ID. User can attach Closed or active sub forms. 4.4.6 View History The user can view history of the form

8

Eform Technical Documentation January 2005

4.4.7

View Route

By clicking the user route button, user view the forms route (Requirement graphical representation) 4.4.8 Publish Report Publish form / reports – this is available through ACCPOL BPM Application – ACCPOL BPM users can export forms / reports to the HTML format. Such published forms can be stored in user’s personal folders. Publish report will be notified to users inbox. User Management Structure Facility

Department

Employee

Division

Designation

User

Module Access

Member

Functionality

Module

Group

Group Policy

Section Policy CostCenter

4.4.9 Form Management (ACCPOL BPM & Reports) Manage Form Instance: View and Search ACCPOL BPM instance in Live or archive server Form Statistics Reports: Provide standard ACCPOL BPM Statistics Report Also ACCPOL BPM admin module provide following functionality:

4.4.10 Scheduler Management Scheduler Task Management: Add/Delete/Edit Scheduler Task Scheduler Task Log Management: View and Search Scheduler task logs Scheduler Report Management: Add/Delete/Edit Scheduler/Pooling Service Task 4.4.11 Digital Signature Digital Signature enables the signature to be captures to provide high level security with authentication while processing the forms.

9

Eform Technical Documentation January 2005

5 Architecture Approach This document covers Basic Design approach such as: ƒ ƒ ƒ ƒ ƒ ƒ

N-Tier Architecture Overview ACCPOL BPM Architecture Overview ACCPOL BPM Database Architecture Base class architecture System Configuration and Parameters Security and Login Process

5.1 N-Tier Architecture Overview

Traditional middle-tier data access (top) might fall by the wayside when compared to a .NET dataset cached on the local server (bottom). This not only decreases latency, it improves application throughput by decreasing overall network utilization

5.2 Scalable Architecture Overview

Server -1 Web Page + Web Service Module Web Client

Load Balancing Server

eForm Database Server -2 Web Page + Web Service Module

10

Eform Technical Documentation January 2005

The Above figure the show the scalable Architecture of ACCPOL BPM system. This architectural approach includes three layers including Database. The Layers are: ƒ ƒ ƒ

Presentation Layer : Web Forms Business & Data Access Layer Database Layer

Scalable Architecture Features ƒ ƒ ƒ ƒ ƒ ƒ

Supports Multiple Web Servers Support web forms Scalable Solution Configurable Transaction logging Configurable Error Logging All user password are Encrypted

11