TIM Wiki / NEW TIM 6 Documentation

A process definition is the predetermined procedure belonging to a process. The process definition provides the framework for all following process instances which are getting initiated. The process definition entails any relevant piece of information which is required to execute the process in T!M. This point subsumes also Smartforms, ActionHandlers, assignments and the diagram of the process itself.

A process instance is a single run determined by a process definition. Every run can be enriched by additional information. This information may be provided regularly by a Smartform and included in the process run.

Smartforms are formulars which can be generated by setting up a process definition. These formulars may merely be used either as containers for data or be used for process-related decisions, for example, if the SmartformDecisionHandler has been used during the modeling stage.

A process variable is being implemented during the course of a process (or, alternatively, a process instance) and accompanies the process from beginning to the end. A process variable can be changed as often as desired. A process variable can be created and changed by using a Smartform or Actionhandler. Process variables can be used to determine the course of processes or to compile several pages of information. Please refer to this page for further information.

The BusinessCalender calculates the time based on working hours and public holidays. The calendar can be adapted to any client. Please refer to this page to get access to a very good introduction about this functionality.

A node is a compilation of tasks. Often, a node will be called an activity in T!M - Task !n Motion which then only entails one task. A node should always be located within a Swimlane to be allotted to an Assignee.

Script nodes do not require any further manipulation by the user. If there is no ActionHandler allotted to the Scrip node then the element will be skipped without provoking any action. Normally, script nodes will be employed to execute an ActionHandler and to provide a clearly arranged overview of the process.

Tasks have to be processed by executive officers within the company and marked as finished before the course of the process may continue.

A (Swim)lane represents a group of users or individual users. A Swimlane contains almost always at least one node. Its role lies in the proper assignment of a task to assignee / executive officer.
If an user has finished a task within a Swimlane he will receive every following task in this specific Swimlane.

Assignees or executive officers are people to whom tasks have been assigned to.