| |
| |
- Ability to alter processes, generating new versions and reflecting the changes in the processes that are being executed.
-
Automatic generation of process forms, with the possibility of using automatically generated or customized forms.
-
Use of application data, custom process roles and attachments with control over document changes (check-in and check-out) and version maintenance.
-
Ability to show or hide data according to the step and security profile of the current user.
Possibility of assigning a domain to the application data, in such a way that the entered data is valid according to its format or with the company’s information system.
-
Use of basic workflow classes (Start, milestone, task, question, notification, evaluation, finalization, sub workflow initiation – subordinate or not -, parallel branch and unification).
-
Specialized steps for the management of documents, data interaction and integration with the components of the organization.
-
Use of alerts, reminders and automatic work assignments, based on work times, fixed date or dates specified by the users or calculated in a previous step.
-
Graphical visualization of the state of all processes and ability to view detailed information regarding tasks and participants involved in them.
-
Change control over process models, implemented by means of check-in and check-out operations which make it easier for people to collaborate in process design tasks without suffering information losses caused by inadequate control management.
-
Hierarchic organization of the processes and elements related to them through a hierarchic structure of packages that favors reuse and security.
-
Role-based security scheme which allows the definition of several types of permission for package access.
|
|
|
| |
|
|
| |
|
|
|
|
|
|
|
|