iGrafx Automation Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
===== Process definition =====
A process definition is the predetermined procedure belonging to a process. The process definition provides the framework for all following [[en:glossar#Prozessinstanz|process instances]] that are initiated. The process definition entails any relevant piece of information which is required to execute the process in TIM. This point also subsumes [[en:glossar#Smartforms]], [[en:software:tim:ActionHandler]]s, assignments and the diagram of the process itself.

----

===== Process instance =====
A process instance is a single run determined by a [[en:glossar#process definition]]. Additional information can be added to every run. This information may be provided regularly by a [[en:glossar#Smartform]] and then included in the process run.

-----

===== Smartform =====
Smartforms are forms which can be generated by setting up a [[en:glossar#process definition]]. These forms may be used either as containers for data or be used for process-related decision making, for example, if the SmartformDecisionHandler has been used during the modeling stage. 

-----

===== Process variable =====
A process variable is actively implemented during the course of a process (or, alternatively, a [[en:glossar#prozessinstanz|process instance]]) and attends to the process from the 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 [[en:software:tim:Smartform]] or an [[en:software:tim:ActionHandler]]. Process variables can be used to manage the course of processes or to compile several pages of information. Please refer to [[en:software:tim:process_variables| this page]] for further information. 
-----


=====  BusinessCalendar =====
The BusinessCalender calculates the time based on working hours and public holidays. The calendar can be adapted to any client. Please refer to [[en:software:tim:calendar_profile|this page]] for a very good introduction to this functionality.

-----

===== Node / activity =====
A node is a compilation of tasks. Often, a node will be called an activity in TIM, which then only entails one task. A node should always be located within a [[en:glossar#swimlane|Swimlane]] in order to be assigned to an [[en:glossar#assignee|Assignee]].

-----

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

-----

===== Tasks =====
Tasks have to be processed by [[en:glossar#assignee_bearbeiter|executive managers]] within the company and marked as finished before the next step of the process may begin. 

-----

===== Swimlane =====
A (Swim)lane represents a group of users or individual users. A Swimlane contains almost always at least one [[en:glossar#node_aktivitaet|node]]. Its role lies in the proper assignment of a [[en:glossar#tasks_aufgabe|task]] to an [[en:glossar#assignee_bearbeiter|assignee / executive manager]]. \\
If an user has finished a task within a [[en:glossar#Swimlane|Swimlane]] he will receive every following task in this specific Swimlane. 
-----

===== Assignee / executive manager =====
Assignees or executive managers are people to whom [[en:glossar#tasks_aufgabe|tasks]] have been assigned. 

-----

===== CBA (Configuration Based Application) =====
iGrafx Automation Wiki

User Tools

Site Tools

Page Tools
