|
| |
|
 |
TeamWARE Flow
is a workflow product that enables teams to plan,
execute participate, track and processes. Processes
can be modelled using TeamWARE ProcessWise WorkBench
and the model exported into TeamWARE Flow. TeamWARE
Flow can also be optionally integrated with other
groupware products including IBM Notes and Microsoft
Exchange. |
|
|
 |
Access to task
list over the WWW. |
|
The Planner provides
business professionals with a graphical process modelling
tool. |
|
The Viewer application
enables teams to participate in processes by viewing
worklists, managing attachments and following process
histories. |
|
The Form Builder
allows professionals to create forms. |
|
Custom integration
with other systems is achieved using the scripting
language, TCL and Application Programming Interface
(API). |
|
Optional system
integration with TeamWARE Office, IBM Notes and Microsoft
Exchange. |
|
Sample applications
and process templates are included. |
| |
|
|
Flexible
Process Management |
|
| Surprises and
exception are common in daily business. TeamWARE
Flow is a new generation of product, designed with
flexibility in mind, to meet the needs of people
who work in varying business situations.
TeamWARE Flow allows
business professionals to improve business through
experimentation and learning. Teams can coordinate
their work by building the work process, following
the progession of the work, and authorized users
can adapt the process when changes are required.
Organizations can
equally well automate and manage formal office processes.
|
|
|
| The Planner allows
professionals to draw up, initiate, and follow up
process plan. Process plan templates are utilized
as a basis when users start new work processes.
Process plans can include roles, forms, sub-plans,
triggers, scripts, parallel and sequential activities,
as well as conditional activities.
|
|
|
| The Viewer shows
worklists, forms, documents and history information
about the process for the team member. By selecting
the work according to the description, priority
or time and then making choices, the user guides
the process forward.
|
|
|
| In addition to
the standard viewer, worklists can be accesed and
work progressed using popular Web browsers.
|
|
|
| Form Builder is
the administration's and programmer's tool for creating
forms for TeamWARE Flow users. The form includes
data fields that are linked to a database and optional
scripts that can, for instances, invoke external
applications.
|
|
Document
Storage and Directories |
|
| Forms, process
plan templates and documents (attached to processes)
are stored in the system. Version control and access
control features depend on the optional integration
with other systems.
Similarly, user information
is stored in a directory system and a range of directory
systems is supported.
|
|
|
| An organization
can start utilizing TeamWARE Flow without any programming.
Custom-built applications can be built to meet specific
system integration or BPR project requirements by
using TeamWARE Flow Application Programming Interface
(API) and embedded scripting language TCL (Tool
Command Language). API supports popular Windows
programming languages (e.g. C++, Visual Basic).
Workflow Management
Coalition's standard interface between the workflow
server and client is supported.
|
|
|
| TeamWARE Flow
can be optionally integrated with the directories,
electronic mail and filestores used in IBM Notes,
Microsoft Exchange or TeamWARE Office.
Multiple server systems
can be built using process migration features.
|
|
|
®TeamWARE is a registered trademark in the USA
and other countries. |
| For
further information contact:
TeamWare endeavours
to ensure that the information in this site is
correct and fairly stated, but does not accept
liability for any error or omission. The development
of TeamWARE products and services is continuous
and published information may not be up to date.
It is important to check the current position
with TeamWARE. This site is not part of a contract
or licence save insofar as may be expressly agreed.
|
|
| |
|
