Plugin installed incorrectly. Rename plugin directory 'swiftmail.backup' to 'swiftmail'.
en:glossar
Differences
This shows you the differences between two versions of the page.
|
en:glossar [2014/12/08 15:34] felix.studnitz |
en:glossar [2021/07/01 09:52] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | FIXME **This page is not fully translated, yet. Please help completing the translation.**\\ //(remove this paragraph once the translation is finished)// | ||
| - | ===== 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]] 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 [[en:glossar#Smartforms]], [[en:software:tim:ActionHandlers]], assignments and the diagram of the process itself. | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ===== Process instance ===== | ||
| - | A process instance is a single run determined by a [[en:glossar#process definition]]. Every run can be enriched by additional information. This information may be provided regularly by a [[en:glossar#Smartform]] and included in the process run. | ||
| - | |||
| - | ----- | ||
| - | |||
| - | ===== Smartform ===== | ||
| - | Smartforms are formulars which can be generated by setting up a [[en:glossar#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. | ||
| - | |||
| - | ----- | ||
| - | |||
| - | ===== Process variable ===== | ||
| - | A process variable is being implemented during the course of a process (or, alternatively, a [[en:glossar#prozessinstanz|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 [[en:software:tim:Smartform]] or [[en:software:tim:Actionhandler]]. Process variables can be used to determine 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]] to get access to a very good introduction about this functionality. | ||
| - | |||
| - | ----- | ||
| - | |||
| - | ===== Node / activity ===== | ||
| - | 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 [[en:glossar#swimlane|Swimlane]] to be allotted 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 Scrip node then the element will be skipped without provoking 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 officers]] within the company and marked as finished before the course of the process may continue. | ||
| - | |||
| - | ----- | ||
| - | |||
| - | ===== 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 [[en:glossar#assignee_bearbeiter|assignee / executive officer]]. \\ | ||
| - | 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 officer ===== | ||
| - | Assignees or executive officers are people to whom [[en:glossar#tasks_aufgabe|tasks]] have been assigned to. | ||
| - | |||
| - | ----- | ||
| - | |||
| - | ===== CBA (Configuration Based Application) ===== | ||
en/glossar.txt · Last modified: 2021/07/01 09:52 (external edit)
Except where otherwise noted, content on this wiki is licensed under the following license: 2013 T!M Solutions GmbH
