Activities in the Process

The activity is the base component of the process and are divided into three main categories.

Default Activity
Client Event	A Client event is defined as a point in the process where human intervention is required
Server Event	A server event is defined as a point in the process where an event takes place at the server that does not require human intervention
Inter Process Communication Event	An IPC Event enables different K2 Processes that are either locally or remotely hosted to be synchronously or asynchronously linked

The activity (Client, Server, or IPC) is an important component in the process because they define points in the process where decisions are made i.e. how data is delivered and what actions are taken. When looking at the properties of an Activity, notice that many of the properties are rules. These rules are Activity Rules, and represent the tool used to build business logic into the Activity.

The Default Activity Wizard creates a new Activity container within the workflow design canvas.

Why use the Default Activity Wizard

Activities act as the containers for events within a process. An Activity within a process can potentially contain Client Events, Server Events or Inter Process Communication (IPC) events. The business logic includes concepts like: a) who must be involved in the Activity, and b) are there any pre-requisites that must be met before workflow participants can start with the Activity. Activities are important components in the process because they represent points where decisions are to be made, data is to be delivered, or actions are to be carried out. One of the most important properties of Activities is the business rules associated with the activity. These Activity Rules represent the tools used to build business logic into the activity. For an activity to be useful, it must have at least one event associated with it.

The Default Activity can only host one Client event, which performs one Client event action. This approach categorizes tasks into single steps where one task is handled per Default Activity. Where multiple steps of Client Event interaction are required in a process, the tasks are linked together by successive default activities each containing one client event.