Background
|
Welcome to the Aspen Workflow Admin Guide. This guide is intended for
administrators. It documents the workflow data structure, setup of the meta data,
and customization.
|
|
|
Include information on the database,
web server, data structure, server and client
configuration as well as security.
|
|
|
Creation of processes, including tasks,
exception sub-process, exception tasks, and task
triggering.
|
|
|
Creation of tasks, including fields and
customizing business logic via javascript.
|
|
|
A field is a piece of information that needs to
be tracked. A field is defined in a row in a table called Field, and
represented in a row in a table called MatterField. This enable the
workflow system to store and track each nugget of information that enters
the system, as well as enabling administrators to expand the system
without programming.
|
|
|
Actions are business rules that are applied
automatically by the Aspen Workflow system. Examples of actions
include customizing processes for various clients and vendors, automate
the sending of emails and reports.
|
|
|
A Team is a group of people that typically perform similar functions.
Every Matter, Process and Task within Aspen Workflow can be assigned to a
Team. |
|
|
A Person is an Aspen Workflow user. They are able to log into the Aspen
Workflow system, add, update and delete Matters, Process,
Tasks, Notes and Documents, subject to security settings. Every Matter, Process and Task within Aspen
Workflow can be assigned to a Person. A Person assigned responsibility for
maintaining the installation-specific customized aspects of Aspen Workflow
is referred to as an Administrator. |
|
|
Designing import and export routines for
integration with Aspen Workflow data structures.
|
|
|
Synchronize data with other systems. |
|
|
Categories are used to control dropdown lists
and generic fields in Aspen Workflow.
|
|
|
System defaults are installation-specific
information used to tailor the behavior of Aspen Workflow for a single
installation.
|
|
|
Aspen Grove certifies Aspen Workflow to be Year
2000 compliant in accordance with the underlying Microsoft products (IIS,
MSSQL and NT 4.0)
|
|
|
To aid in understanding the matter, process, task and field tables.
|
|
|
This includes items such as Notes, License Agreements.
|