Glossary

Process Engine

Process Engine is the workhorse behind the BPM. The process engine consists of two types of engines - one process interpreter and one or more task executors.

Task

A Task is a type of Activity/Flow Object within a Process flow. It represents the finest level of detail in the process execution. Either the end-user or the application itself can be used to perform the Task when it is executed

Process Instance

A Process itself is a kind of template that defines what will happen during the process flow. Starting a process actually means creating and running a process instance based on this process "template". Multiple Process Instances of one particular Process can run at the same time.

Task Executor

The Task Executor program performs the script and service tasks contained in the running Process Instances, provided the Process Interpreter is running.

Process Interpreter

The Process Interpreter starts new process instances and takes care of the progress in running process instances on the basis of fulfilled conditions in individual process steps.

KPI (SLA)

Customers buy a service from a service provider. A contract defines conditions under which a service will be consumed, known as SLA(Service Level Agreement). Different customers can have different SLAs for the the same service. SLA defines conditions referring to KPIs(Key Performance Indicator) of a service and consequence(an action to apply) if a condition is/is not met.

Usage Examples

SLA conditions

• Prio 1 incident reaction time has to be below 60 minutes
• Time to install a new workplace must be below:
  • 9 business hours, provided the order refers only to standard components
  • 20 business hours, provided the order refers to non-standard components
• A disk quota of 50% or less was consumed in the last month and a total CPU time in month was below 200 hours
• Prio 1 incident reaction time was above 60 minutes 10% of the time over the last week

SLA actions

• Price increase of 10%
• Price discount of 1%
• Bonus time for free

Miscellaneous

Is there any limitation to which amount of users a User Task can be offered?

Amount of users to which a User Task can be offered is limited to approx. 500.

When a User Task is offered to a User Group, identification of all users composing the group, in the form "-ID1-ID2-ID3-", is stored in the attribute "AMT_BPMWORKITEM.USERIDS" which has limited length 4000 characters.

Why do I have a Java error while trying to use web services?

Java JDK is required to user web services - JRE is not suitable.