Risultati della ricerca
Da itm wiki.
Crea la pagina "Workflow" su questo wiki! Vedi anche i risultati della ricerca
Corrispondenze nel titolo delle pagine
- ...''[[glossary|workflow fields]]''. Privileges are defined per ''[[glossary|workflow status]]'' and ''[[glossary|roles]]''. ...tus''</u> configuration tab; see [[Workflow configuration steps - Statuses|workflow configuration steps - statuses]] for more information) to be present in the6 KB (990 parole) - 16:00, 5 nov 2017
- By using the <u>''Fields''</u> form of ''[[glossary|workflow]]'' configuration it is possible to manage the following: - predefined ''[[glossary|workflow fields]]'' labels3 KB (430 parole) - 15:29, 5 gen 2016
- ...you to quickly start with itmSUITE®, in particular with the ''[[glossary|workflow engine]]'' configuration. Workflow configuration steps.2 KB (219 parole) - 08:38, 4 nov 2017
- This page contains detailed information on the configuration of ''[[glossary|workflow fields]]''. == Predefined workflow fields configuration ==13 KB (2 238 parole) - 12:01, 6 nov 2017
- #REDIRECT [[Workflow engine configuration]]43 byte (4 parole) - 16:53, 14 apr 2015
- ...tion of ''[[glossary|workflows]] ''by means of its embedded ''[[glossary|workflow engine]].'' ...]''[[glossary|s]] can be exported and re-imported by means of ''[[glossary|workflow cartridges]]''.2 KB (287 parole) - 08:39, 4 nov 2017
- ...]'' configuration is optional and needed only if, in a target ''[[glossary|workflow]]'', you plan to use ''[[glossary|ticket activities]]''.2 KB (357 parole) - 17:29, 14 gen 2016
- ...done once but it may require updates before configuring a new ''[[glossary|workflow]]''. ...w/Ticket Types''''' || ''[[glossary|Ticket types]]'' are a key element of workflow management and they can be configured through this functionality.2 KB (338 parole) - 21:48, 15 nov 2015
- ...available, by default, at the following menu entry: '''''General/WorkFlow/WorkFlow Engine'''''. The list of available ''[[glossary|workflows]]'' appears as in [[File:Workflow list screen.JPG|left|thumb|840x840px|Workflows list screen]]7 KB (1 078 parole) - 10:08, 4 nov 2017
- ...For example, the status "Closed" generally indicates that the ''[[glossary|workflow]]'' occurrence is completed and no other activity can be performed. ...managed in the ''<u>Associated Op. Statuses</u>'' tab of the ''[[glossary|workflow]]'' management forms, which appears as in the screen below.2 KB (302 parole) - 10:27, 4 nov 2017
- ...''[[glossary|workflow transitions]]''. The list of configured ''[[glossary|workflow transitions]]'' is listed when entering. ...px|Workflow Transitions list screen]]It is possible add a new ''[[glossary|workflow transition]]'' with the '''ADD NEW''' command or edit an existing configura7 KB (1 043 parole) - 07:54, 22 nov 2015
- == Creating a workflow form == ...b of a ''[[glossary|ticket]]''. This is done by configuring a ''[[glossary|workflow form]] ''which is constituted of a set of sections and columns.4 KB (704 parole) - 21:19, 10 gen 2016
- ...be configured in the ''<u>Transition Rule</u>'' tab (see the dedicated [[Workflow configuration steps - Transitions|configuration page]]). == Workflow related notifications ==5 KB (736 parole) - 21:29, 14 gen 2016
- ...received) ''[[glossary|messages]]'' related to them. Based on ''[[glossary|workflow]]'', it can be useful to create some message templates in order to standard ...age Templates''</u> in the <u>''Grant Management''</u> tab of ''[[glossary|workflow]]'' configuration allows to create any standard ''[[glossary|message templa2 KB (339 parole) - 21:52, 14 gen 2016
- #REDIRECT [[Workflow Engine Configuration]]43 byte (4 parole) - 07:57, 3 nov 2017
- ...'' form/tab of the ''[[glossary|tickets]]'' associated to the ''[[glossary|workflow]]''. If none is selected, the default ''[[glossary|ASM view]]'' is used.262 byte (50 parole) - 16:20, 5 nov 2017
- ...'[[glossary|workflow field]]'' based on two other influencing ''[[glossary|workflow fields]]''. ...ld]]''. If you want to keep the existing value for the target ''[[glossary|workflow field]]'', set the "Keep Current" value.1 KB (252 parole) - 16:43, 5 nov 2017
- ...a ''[[glossary|workflow transition]]'' or viewing/updating a ''[[glossary|workflow field]]''. ...you won't be able to set privileges relating to them for the ''[[glossary|workflow]]''elsewhere.681 byte (114 parole) - 16:50, 5 nov 2017
- This form/tab allows to manage visibility of the values of some ''[[glossary|workflow fields]]'' per ''[[glossary|project]]'' / ''[[glossary|service]]''. See [[212 byte (34 parole) - 19:51, 5 nov 2017
- ...ry|workflow]]''. This means that no two instances of the same ''[[Glossary|workflow]]'' (i.e. ''[[Glossary|tickets]]'') may have the same values for the elemen To define a unique key, just add all the ''[[Glossary|workflow fields]]'' that shall be part of it.352 byte (67 parole) - 20:36, 5 nov 2017
Corrispondenze nel testo delle pagine
- * [[Workflow Engine]]2 KB (293 parole) - 11:31, 22 nov 2017
- * [[Workflow Engine Configuration|Workflow Engine]] * [[Workflow fields configuration|Workflow fields configuration]]5 KB (534 parole) - 10:56, 11 giu 2018
- ...fine ''[[Glossary|Metrics]]'' and notifications for different ''[[Glossary|Workflow]]''. ...</u> || Lead time for workflow (status A -> status B), Group lead time for workflow (status A -> status B), Difference between date fields, Difference between13 KB (2 091 parole) - 10:36, 30 mag 2018
- ...y|workflow engine]]''. A set of pre configured processes are supplied as ''workflow cartridges'', in particular: However, ''[[Glossary|SM]]'' ''[[Glossary|workflow engine]]'' is very flexible and powerful and may support many other busines2 KB (267 parole) - 10:43, 18 feb 2016
- ...''Changes'' are managed through the ''change management'' process and a ''workflow cartridge'' is available for the ''SM'' ''module'' which supports its execu ...beneficial changes to be made with minimum disruption to IT services. A ''workflow cartridge''is is made available for the ''SM module ''which supports the ex49 KB (6 974 parole) - 10:36, 12 giu 2018
- It includes a powerful ''[[Glossary#W|workflow engine]]'' that allows freely configurable to support the execution of the The configurable ''[[Glossary#W|workflow engine]]'' is almost unlimited and makes this form able to support other pr13 KB (1 951 parole) - 12:48, 1 apr 2015
- * Flexible and codeless management of the workflow configuration for the punctual management of requests, without compromises. ...offers management possibilities for any organisation that has a manageable workflow, for example problem, ''[[Glossary#C|change]]'', improvement actions etc.53 KB (7 777 parole) - 15:45, 26 giu 2015
- ...''[[glossary|workflow fields]]''. Privileges are defined per ''[[glossary|workflow status]]'' and ''[[glossary|roles]]''. ...tus''</u> configuration tab; see [[Workflow configuration steps - Statuses|workflow configuration steps - statuses]] for more information) to be present in the6 KB (990 parole) - 16:00, 5 nov 2017
- By using the <u>''Fields''</u> form of ''[[glossary|workflow]]'' configuration it is possible to manage the following: - predefined ''[[glossary|workflow fields]]'' labels3 KB (430 parole) - 15:29, 5 gen 2016
- ...Management]]'' process is supported by a ''[[Glossary|SM]]'' ''[[Glossary|workflow cartridge]]'' that enables the execution of the process according to the IT ...l configuration will still be required. To this aim, the [[Workflow engine|Workflow Engine]] guide may be useful.34 KB (5 342 parole) - 15:41, 26 giu 2015
- ...you to quickly start with itmSUITE®, in particular with the ''[[glossary|workflow engine]]'' configuration. Workflow configuration steps.2 KB (219 parole) - 08:38, 4 nov 2017
- This page contains detailed information on the configuration of ''[[glossary|workflow fields]]''. == Predefined workflow fields configuration ==13 KB (2 238 parole) - 12:01, 6 nov 2017
- #REDIRECT [[Workflow engine configuration]]43 byte (4 parole) - 16:53, 14 apr 2015
- ...Fulfilment]]'' process is supported by a ''[[Glossary|SM]]'' ''[[Glossary|workflow cartridge]]'' that enables the execution of the process according to the IT ...l configuration will still be required. To this aim, the [[Workflow engine|Workflow Engine]] guide may be useful.33 KB (5 131 parole) - 10:54, 10 mag 2016
- ...management]]'' process is supported by a ''[[Glossary|SM]]'' ''[[Glossary|workflow cartridge]]'' that enables the execution of the process. ...l configuration will still be required. To this aim, the [[Workflow engine|Workflow Engine]] guide may be useful.26 KB (4 122 parole) - 14:03, 9 mag 2016
- ...Management]]'' process is supported by a ''[[Glossary|SM]]'' ''[[Glossary|workflow cartridge]]'' that enables the execution of the process according to the IT ...l configuration will still be required. To this aim, the [[Workflow engine|Workflow Engine]] guide may be useful.36 KB (5 552 parole) - 15:21, 7 mag 2017
- 2 KB (322 parole) - 15:35, 28 ago 2015
- ...Management]]'' process is supported by a ''[[Glossary|SM]]'' ''[[Glossary|workflow cartridge]]'' that enables the execution of the process according to the IT ...l configuration will still be required. To this aim, the [[Workflow engine|Workflow Engine]] guide may be useful.39 KB (5 855 parole) - 11:20, 18 lug 2015
- ...Management]]'' process is supported by a ''[[Glossary|SM]]'' ''[[Glossary|workflow cartridge]]'' that enables the execution of the process according to the IT ...l configuration will still be required. To this aim, the [[Workflow engine|Workflow Engine]] guide may be useful.33 KB (4 961 parole) - 15:01, 10 mag 2016
- ...tion of ''[[glossary|workflows]] ''by means of its embedded ''[[glossary|workflow engine]].'' ...]''[[glossary|s]] can be exported and re-imported by means of ''[[glossary|workflow cartridges]]''.2 KB (287 parole) - 08:39, 4 nov 2017
- Workflow Button ===== Workflow Button =====22 KB (2 795 parole) - 17:06, 6 nov 2017
- ...Management]]'' process is supported by a ''[[Glossary|SM]]'' ''[[Glossary|workflow cartridge]]'' that enables the execution of the process according to the IT ...l configuration will still be required. To this aim, the [[Workflow engine|Workflow Engine]] guide may be useful.31 KB (4 499 parole) - 10:15, 27 apr 2017
- ...ment Change]]'' process is supported by a ''[[Glossary|SM]]'' ''[[Glossary|workflow cartridge]]'' that enables the execution of the process. This process is st ...l configuration will still be required. To this aim, the [[Workflow engine|Workflow Engine]] guide may be useful.16 KB (2 520 parole) - 17:53, 28 ott 2015
- ...]'' configuration is optional and needed only if, in a target ''[[glossary|workflow]]'', you plan to use ''[[glossary|ticket activities]]''.2 KB (357 parole) - 17:29, 14 gen 2016
- ...done once but it may require updates before configuring a new ''[[glossary|workflow]]''. ...w/Ticket Types''''' || ''[[glossary|Ticket types]]'' are a key element of workflow management and they can be configured through this functionality.2 KB (338 parole) - 21:48, 15 nov 2015
- ...available, by default, at the following menu entry: '''''General/WorkFlow/WorkFlow Engine'''''. The list of available ''[[glossary|workflows]]'' appears as in [[File:Workflow list screen.JPG|left|thumb|840x840px|Workflows list screen]]7 KB (1 078 parole) - 10:08, 4 nov 2017
- ...For example, the status "Closed" generally indicates that the ''[[glossary|workflow]]'' occurrence is completed and no other activity can be performed. ...managed in the ''<u>Associated Op. Statuses</u>'' tab of the ''[[glossary|workflow]]'' management forms, which appears as in the screen below.2 KB (302 parole) - 10:27, 4 nov 2017
- ...''[[glossary|workflow transitions]]''. The list of configured ''[[glossary|workflow transitions]]'' is listed when entering. ...px|Workflow Transitions list screen]]It is possible add a new ''[[glossary|workflow transition]]'' with the '''ADD NEW''' command or edit an existing configura7 KB (1 043 parole) - 07:54, 22 nov 2015
- == Creating a workflow form == ...b of a ''[[glossary|ticket]]''. This is done by configuring a ''[[glossary|workflow form]] ''which is constituted of a set of sections and columns.4 KB (704 parole) - 21:19, 10 gen 2016
- ...be configured in the ''<u>Transition Rule</u>'' tab (see the dedicated [[Workflow configuration steps - Transitions|configuration page]]). == Workflow related notifications ==5 KB (736 parole) - 21:29, 14 gen 2016
- ...received) ''[[glossary|messages]]'' related to them. Based on ''[[glossary|workflow]]'', it can be useful to create some message templates in order to standard ...age Templates''</u> in the <u>''Grant Management''</u> tab of ''[[glossary|workflow]]'' configuration allows to create any standard ''[[glossary|message templa2 KB (339 parole) - 21:52, 14 gen 2016
- |''Workflow'' || || '''X''' || '''X''' ...ypes</u> || '''''Ticket Type''''' || Primary || multiselected filter for ''Workflow'' Ticket Types10 KB (1 383 parole) - 10:07, 16 ott 2018
- == Business case managed through a [[glossary|workflow]] == ...) is to manage the business case (and its approval) through a ''[[glossary|workflow]]''. This requires that the [[SM - Service Desk and Service Management|SM -5 KB (761 parole) - 15:06, 5 apr 2016
- ...ould be designed to execute a product quality inspection. The ''[[glossary|workflow]]'' records (and associated reporting) can be used to implement the quality3 KB (396 parole) - 17:02, 5 apr 2016
- #REDIRECT [[Workflow Engine Configuration]]43 byte (4 parole) - 07:57, 3 nov 2017
- ...'' form/tab of the ''[[glossary|tickets]]'' associated to the ''[[glossary|workflow]]''. If none is selected, the default ''[[glossary|ASM view]]'' is used.262 byte (50 parole) - 16:20, 5 nov 2017
- ...'[[glossary|workflow field]]'' based on two other influencing ''[[glossary|workflow fields]]''. ...ld]]''. If you want to keep the existing value for the target ''[[glossary|workflow field]]'', set the "Keep Current" value.1 KB (252 parole) - 16:43, 5 nov 2017
- ...a ''[[glossary|workflow transition]]'' or viewing/updating a ''[[glossary|workflow field]]''. ...you won't be able to set privileges relating to them for the ''[[glossary|workflow]]''elsewhere.681 byte (114 parole) - 16:50, 5 nov 2017
- ...MDMM]]'' functionality enables to condition the visibility of ''[[glossary|workflow fields]]'' values base on the ''[[glossary|project]]'' / ''[[glossary|servi For example a ''[[glossary|workflow field]]'' might have three values, "1", "2" and "3". With ''[[glossary|MDMM1 KB (195 parole) - 20:16, 5 nov 2017
- This form/tab allows to manage visibility of the values of some ''[[glossary|workflow fields]]'' per ''[[glossary|project]]'' / ''[[glossary|service]]''. See [[212 byte (34 parole) - 19:51, 5 nov 2017
- ...ry|workflow]]''. This means that no two instances of the same ''[[Glossary|workflow]]'' (i.e. ''[[Glossary|tickets]]'') may have the same values for the elemen To define a unique key, just add all the ''[[Glossary|workflow fields]]'' that shall be part of it.352 byte (67 parole) - 20:36, 5 nov 2017
- == Workflow level logging ==1 KB (198 parole) - 21:18, 5 nov 2017
- For an Event Type generated by WorkFlow Transition is not possible to update the Notification Template here. The Notification Template shall be updated in WorkFlow Engine.19 KB (2 520 parole) - 14:54, 28 nov 2017
- # A special field called <u>''Custom field''</u> has to be choosen if a ''workflow'' ''custom field'' has to be added to the ''forced view''.9 KB (1 490 parole) - 07:29, 22 mag 2018
- |SOLUTIONGROUP_ID || int (4)|| Group reference id. At each group per workflow is assigned a specific role. |WORKFLOW_ID || int (4)|| Workflow reference id27 KB (3 660 parole) - 15:07, 22 nov 2018
- The Ticket custom field may be defined in General\WorkFlow\Custom Fields.9 KB (1 491 parole) - 15:09, 15 giu 2018
- ...o an Organization unit. For further detail about this subject refer to ''[[Workflow Engine Configuration]]'' ...with Role "Requester". For further detail about this subject refer to ''[[Workflow Engine Configuration]]'' or ''[[Timesheet Management]]''22 KB (3 423 parole) - 09:40, 5 ago 2019