|
|
| Riga 4: |
Riga 4: |
| | ''[[glossary|Workflow statuses]]'' are managed in the ''<u>Associated Op. Statuses</u>'' tab of the ''[[glossary|workflow]]'' management forms. | | ''[[glossary|Workflow statuses]]'' are managed in the ''<u>Associated Op. Statuses</u>'' tab of the ''[[glossary|workflow]]'' management forms. |
| | | | |
| − | When a new ''[[glossary|workflow]]'' is created, a set of 'legacy' ''[[glossary|workflow statuses]]'' are generated. For ''[[glossary|workflows]] ''with <u>Associated Entity</u> "Ticket", the initial set of ''[[glossary|workflow statuses]]'' is the following. | + | When a new ''[[glossary|workflow]]'' is created, a set of 'legacy' ''[[glossary|workflow statuses]]'' are generated. For ''[[glossary|workflows]] ''with <u>Associated Entity</u> "Ticket", the initial set of ''[[glossary|workflow statuses]]'' is the following. |
| | | | |
| − | Type. itmSUITE® call it ''[[Glossary|Ticket type]]''.
| |
| − | * Status ''[[Glossary|Workflow status]]''
| |
| − | * How ''[[Glossary|Workflow status]]'' are connecting. Is only a one direction transtion, from status A to B, or we can came back to A, bidirectional transition.
| |
| − | * Which one of the idenfied ''[[Glossary|Workflow status]]' is a Final Status?''
| |
| − |
| |
| − | Once we have drawn our process we have to think which ''[[Glossary|Resource]]'' , or better witch ''[[Glossary|Role]]'' can be enabled to execute the transition. Then we can design the Form and give a grant to the ''[[Glossary|Resource]]. ''
| |
| − |
| |
| − | === Workflow Roles ===
| |
| − |
| |
| − | The li
| |
| − |
| |
| − | At workflow level a user can be configure with 17 ''[[Glossary|roles]]''. ''[[Glossary|Roles]]'' can be:
| |
| − | * Static , Application Level type
| |
| − | * Dynamic , Project / Service or Workflow roles type
| |
| − |
| |
| − | Static ''[[Glossary|Role]]'' are the once assigned to the user, Dynamic role are configured to the resource due to is belonging to a ''[[Glossary|Service]]'' or a ''[[Glossary|Solution Group]]'' or a ''[[Glossary|Client Organization Unit ]]'' or because the resource act as Creator of ''[[Glossary|Ticket]]''
| |
| − |
| |
| − | Here below the table with the role description:
| |
| | | | |
| | {| class="wikitable" | | {| class="wikitable" |
| − | ! Role !! Type !! Note | + | ! Status !! Note |
| | | | |
| | |- | | |- |
| − | |Requester || ''static'' || Assigned to a ''[[Glossary|User]]'' inherited by a ''[[Glossary|resource]]'' | + | |Default || |
| − | |-
| |
| − | |Resource || ''static'' || Assigned to a ''[[Glossary|User]]'' inherited by a ''[[Glossary|resource]]''
| |
| − | |-
| |
| − | |Project manager|| ''static'' || Assigned to a ''[[Glossary|User]]'' inherited by a ''[[Glossary|resource]]''
| |
| − | |-
| |
| − | |Manager|| ''static'' || Assigned to a ''[[Glossary|User]]'' inherited by a ''[[Glossary|resource]]''
| |
| − | |-
| |
| − | |Administrator|| ''static'' || Assigned to a ''[[Glossary|User]]'' inherited by a ''[[Glossary|resource]]''
| |
| − | |-
| |
| − | |Assegnee|| ''dynamic'' || ''[[Glossary|resource]]'' that has assigned a ''[[Glossary|ticket activity]]''
| |
| − | |-
| |
| − | |Creator|| ''dynamic'' || ''[[Glossary|resource]]'' that create a ''[[Glossary|ticket ]]''
| |
| − | |-
| |
| − | |Master SG Member|| ''dynamic'' || ''[[Glossary|resource]]'' included in ''[[Glossary|Master Solution Gruop ]]''
| |
| − | |-
| |
| − | |Master SG Manager|| ''dynamic'' || Manager of ''[[Glossary|Master Solution Gruop ]]''
| |
| − | |-
| |
| − | |OU Manager|| ''dynamic'' ||Client ''[[Glossary|Organization Unit ]]'' manager
| |
| − | |-
| |
| − | |Owner|| ''dynamic'' ||''[[Glossary|resource]]'' responsible for the ticket ''[[Glossary|ticket ]]''
| |
| − | |-
| |
| − | |SG Manager|| ''dynamic'' ||Manager of ''[[Glossary|Solution Gruop ]]''
| |
| − | |-
| |
| − | |Solution group member|| ''dynamic'' || ''[[Glossary|resource]]'' that belong to ''[[Glossary|Solution Gruop ]]''
| |
| | |- | | |- |
| − | |TA SG Manager|| ''dynamic'' || Manager of ''[[Glossary|Solution Gruop ]]'' assigned to ''[[Glossary|ticket ]]'' | + | |Opened || |
| | |- | | |- |
| − | |Third level solution group|| ''dynamic'' || ''[[Glossary|resource]]'' that belong to ''[[Glossary|Third Solution Gruop ]]'' | + | |Closed || |
| | |- | | |- |
| − | |Ticket requester|| ''dynamic'' || ''[[Glossary|resource]]'' that has been marked as requester into ''[[Glossary|ticket ]]'' | + | |Completed || |
| | |- | | |- |
| − | |Ticket worker|| ''dynamic'' || ''[[Glossary|resource]]'' that has in charge the ''[[Glossary|ticket ]]'' | + | |Cancelled || |
| | | | |
| | |} | | |} |
| − |
| |
| − | === Workflow Status ===
| |
| − |
| |
| − | itmSUITE® enable the user to create how many status is needed to deploy is workflow. When the user create the workflow, the system create for him 9-legacy status:
| |
| − |
| |
| − | * Default
| |
| − | * Opened
| |
| − | * Defined
| |
| − | * Runinng
| |
| − | * In Charge
| |
| − | * Completed
| |
| − | * Closed
| |
| − | * Reopened
| |
| − | * Cancelled
| |
| − |
| |
| − | this status are called legacy, because the system act in a particular way when they are reached by ''[[Glossary|ticket ]]''
| |
| − |
| |
| − | The ''[[Glossary | Administrator]]'' can create others ''[[Glossary|status]]'' that will be used to drown the desire workflow
| |
| − |
| |
| − | === Define a Transition ===
| |
| − |
| |
| − | Transition are the connection between ''[[Glossary|status]]''. Definie a transition means:
| |
| − | * select starting ''[[Glossary|status]]'' , say Defualt
| |
| − | * select ending ''[[Glossary|status]]'' , say Opened
| |
| − | * choose the ''[[Glossary|role]]'' authorized to perform this transtion, e.g. Creator
| |
| − | We can create a One-way transition or bi-directional transition.
| |
| − |
| |
| − | Many [[Glossary|roles]] can be enabled to perform a single transition.
| |
| − |
| |
| − | === Form Designer ===
| |
| − |
| |
| − | User interact with the workflow via ''[[Glossary|Ticket form]]''. To create a Ticket form the ''[[Glossary|administator]]'' can :
| |
| − |
| |
| − | * Identify the necessary standard field
| |
| − | * Create custom field
| |
| − | * Create Form layout
| |
| − |
| |
| − | Form designer , think a form as a blank page, than the ''[[Glossary|administator]]'' can create Sections, and devide it in columns and compose the page inserting the fields.
| |
| − |
| |
| − |
| |
| − | === Grant Management ===
| |
| − |
| |
| − | ''[[Glossary | Administrator]]'' can keep Visible or Mandatory some field based on ''[[Glossary | Ticket Status]]''and
| |
| − | ''[[Glossary | Resource role]]''
| |
| − |
| |
| − | For example, ''[[Glossary | Ticket creator]]'' see the necessary fields to define an issue, but ''[[Glossary| Service desk operator]]'' that keep in charge the issue has available the first set of fields plus the once necessary to Categorize and Analyse the issue. When the ''[[Glossary | Ticket ]]'' will be completed the ''[[Glossary | Ticket creator]]'' should have the orignal set of fields plus the solution.
| |
