Differenze tra le versioni di "Workflow configuration steps - Creation and basic settings"

Da itm wiki.
(→‎Basic settings)
(Etichetta: visualeditor)
(→‎Basic settings)
 
(22 versioni intermedie di uno stesso utente non sono mostrate)
Riga 30: Riga 30:
  
 
|}
 
|}
 +
The '''CHANGE STATUS''' command allows to change the status of the <u>Status</u> (see [[#Basic settings|Basic settings]]) of the ''[[glossary|workflow]]'' for one or more selected at the same time.
  
 
== Basic settings ==
 
== Basic settings ==
Riga 44: Riga 45:
  
 
|-
 
|-
−
| <u>Status</u> || The status of the ''[[glossary|workflow]]''. || The default status at creation time is "Provisory". When the mandatory settings are defined, the ''[[glossary|workflow]]'' can be set to "Active". In this status it can be executed. Finally, it cab be set to "Inactive" if all instances of the ''workflow'' are closed.
+
| <u>Status</u> || The status of the ''[[glossary|workflow]]''. || The default status at creation time is "Provisory". When the mandatory settings are defined, the ''[[glossary|workflow]]'' can be set to "Active". In this status it can be executed. Finally, it can be set to "Inactive" if all instances of the ''workflow'' are closed. Only ''[[glossary|workflows]]'' in <u>Status</u> "Active" can be created and executed. The system warns if there are constraints avoiding the change of status with a message.
  
 
|-
 
|-
Riga 60: Riga 61:
  
 
|-
 
|-
−
| <u>Associated Entity</u> || To identify the type of ''[[glossary|workflow]]'' which will be configured. || The available values are "Ticket" and "News". The "News" value shall be selected if
+
| <u>Associated Entity</u> || To identify the type of ''[[glossary|workflow]]'' which will be configured. || The available values are "Knowledge", "News", "Project/Service" and "Ticket".
 +
The "Knowledge" value shall be selected to design and implement ''[[glossary|workflow]]''(s) for publishing ''[[glossary|knowledge]]'' in ''[[glossary|knowledge portal]]''(s). The "News" value shall be selected to design and implement ''[[glossary|workflow]]''(s) for publishing ''[[glossary|news]]''. The "Project/Service" value shall be selected to design and implement ''[[glossary|workflow]]''(s) intended to manage the information of ''[[glossary|project]]''s or ''[[glossary|service]]''s. "Ticket" shall be selected for all other ''[[glossary|workflow]]''s.
  
 
|-
 
|-
−
| Ticket Type || Tbd || Tbd
+
| <u>Ticket Type</u> || This field defines the ''[[glossary|ticket type]]'' to which the ''[[glossary|workflow]]'' applies. || This is a mandatory field. Only one ''[[glossary|workflow]]'' can be created for a specific ''[[glossary|ticket type]]'' - ''[[glossary|project]]''/''[[glossary|service]]'' (see <u>Project/Service</u> field).
  
 
|-
 
|-
−
| Projec/Service || Tbd || Tbd
+
| <u>Projec/Service</u> || One or more ''[[glossary|project(s)]]'' or ''[[glossary|service(s)]]'' to which the ''[[glossary|workflow]]'' applies. || At least one'' [[glossary|project]]/[[glossary|service]]'' shall be selected to create a ''[[glossary|workflow]]''.
  
 
|-
 
|-
−
| Description || Tbd || Tbd
+
| <u>Description</u> || A textual description of the ''[[glossary|workflow]]'' (e.g. aim and other details). ||  
  
 
|-
 
|-
−
| WF Sender || Tbd || Tbd
+
| <u>WF Sender</u> || The mailbox configuration from which the the ''[[glossary|messages]]'' related to the ''[[glossary|workflow]]'' will be sent. || The possible mailboxes are defined in the ''[[glossary|company]]'' settings ('''''General/Company/Company Info'''''), in the ''<u>Mail Options</u>'' tab.
  
 
|-
 
|-
−
| Resource Allocation Mode For Transition Rule || Tbd || Tbd
+
| <u>Resource Allocation Mode For Transition Rule</u> || This sets the mode to manage new ''[[glossary|resources]]'' for the ''[[glossary|workflow]]'' when they are added to the system. || If "Dynamic" is selected, a new ''[[glossary|resource]]'' is automatically added (enabled) to the ''[[glossary|workflow transitions]]'' based on his/her ''[[glossary|application level role]]'' and the'' [[glossary|workflow]]'' configurations for them. If "Static" this won't be done and no authorization will be granted concerning ''[[glossary|application level role]]'' ''[[glossary|workflow transition]]'' rights configuration when a new ''[[glossary|resource]]'' is added.
  
−
|}
+
|-
 +
| <u>Show Short Description on Ticket Tab</u> || If enabled, the short description of the of the ''[[glossary|workflow]]'' is displayed in the form of the ''[[glossary|ticket]]''(s) opened on it. ||
  
−
Type.  itmSUITE® call it ''[[Glossary|Ticket type]]''.
+
|-
−
*  Status ''[[Glossary|Workflow status]]''
+
| <u>Related Ticket View</u> || Sets the ''[[glossary|view]]'' which is used in the ''<u>Ticket</u>'' form/tab of ''[[glossary|ticket]]''(s). ||  
−
*  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"
 
−
! Role !! Type !! Note
 
−
 
−
|-
 
−
|Requester || ''static'' || Assigned to a  ''[[Glossary|User]]''  inherited by a  ''[[Glossary|resource]]''
 
−
|-
 
−
|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 ]]''
 
−
|-
 
−
|Third level solution group|| ''dynamic'' || ''[[Glossary|resource]]'' that belong to ''[[Glossary|Third Solution Gruop ]]''
 
−
|-
 
−
|Ticket requester|| ''dynamic'' || ''[[Glossary|resource]]'' that has been marked as requester into ''[[Glossary|ticket ]]''
 
 
|-
 
|-
−
|Ticket worker|| ''dynamic'' || ''[[Glossary|resource]]'' that has in charge the ''[[Glossary|ticket ]]''
+
| <u>Related Ticket Tab Preview</u> || Sets the ''[[glossary|view]]'' which is shown when  the ''<u>Ticket</u>'' form/tab info of ''[[glossary|ticket]]''(s) is activated. ||
  
 
|}
 
|}
 +
The '''MANAGE SETTINGS FOR PROJECTS/SERVICES''' command allows to configure some settings for one or more ''[[glossary|project(s)]]''/''[[glossary|service(s)]]'' related to the ''[[glossary|workflow]]'' as those configured for a master ''[[glossary|project]]''/''[[glossary|service]]''. Configurations which can be set separately are those defined for the master and concerning ''[[glossary|transitions]] ''(''[[glossary|roles]]'', ''[[glossary|resources]]'' and ''[[glossary|VCE conditions]]'' settings), outbound ''[[glossary|notifications]]'' (''[[glossary|roles]]'', ''[[glossary|resources]]''), ''[[glossary|workflow notifications]]'' and ''[[glossary|MDMM]]'' definitions.
  
−
=== Workflow Status ===
+
The '''EXPLORE WORKFLOW''' command allows to graphically explore how the ''[[glossary|workflow]]'' is configured as a results of its settings.
−
 
 
−
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.
+
The '''EXPORT''' command allows to export the ''[[glossary|workflow]]'' settings for backup and/or later import. Specifically, the privileges configuration for ''[[glossary|workflow transition]]''s are saved in an excel file for each ''[[glossary|workflow status]]''.

Versione attuale delle 10:08, 4 nov 2017

List management and creation

The list of workflows and functionalities to update and create new workflows are by default made available, by default, at the following menu entry: General/WorkFlow/WorkFlow Engine. The list of available workflows appears as in the screen below.

Workflows list screen

In the screen some commands are made available by means of specific buttons:

Command Performed functionality
DELETE Deletes one or more selected workflows.
CHANGE STATUS TO BE CHECKED
ADD NEW Adds a new workflow.
COPY Copy the selected workflow.
FILTER Enables to filter the list of workflows.
DROP FILTER Removes any previously applied filter to the list of workflows.
PRINT LIST Prints the listed workflows.

The CHANGE STATUS command allows to change the status of the Status (see Basic settings) of the workflow for one or more selected at the same time.

Basic settings

After creating a new workflow with the ADD NEW command, it is possible to complete its basic configuration by editing the following screen.

Workflow General screen

The following fields can be managed:

Field Purpose Comments
Code The identifier of the workflow. Automatically assigned.
Status The status of the workflow. The default status at creation time is "Provisory". When the mandatory settings are defined, the workflow can be set to "Active". In this status it can be executed. Finally, it can be set to "Inactive" if all instances of the workflow are closed. Only workflows in Status "Active" can be created and executed. The system warns if there are constraints avoiding the change of status with a message.
Creation User The user who created the workflow. Automatically assigned.
Edit User The user who last edited the workflow. Automatically assigned.
Creation Date The creation date of the workflow. Automatically assigned.
Edit Date The last edit date of the workflow. Automatically assigned.
Associated Entity To identify the type of workflow which will be configured. The available values are "Knowledge", "News", "Project/Service" and "Ticket".

The "Knowledge" value shall be selected to design and implement workflow(s) for publishing knowledge in knowledge portal(s). The "News" value shall be selected to design and implement workflow(s) for publishing news. The "Project/Service" value shall be selected to design and implement workflow(s) intended to manage the information of projects or services. "Ticket" shall be selected for all other workflows.

Ticket Type This field defines the ticket type to which the workflow applies. This is a mandatory field. Only one workflow can be created for a specific ticket type - project/service (see Project/Service field).
Projec/Service One or more project(s) or service(s) to which the workflow applies. At least one project/service shall be selected to create a workflow.
Description A textual description of the workflow (e.g. aim and other details).
WF Sender The mailbox configuration from which the the messages related to the workflow will be sent. The possible mailboxes are defined in the company settings (General/Company/Company Info), in the Mail Options tab.
Resource Allocation Mode For Transition Rule This sets the mode to manage new resources for the workflow when they are added to the system. If "Dynamic" is selected, a new resource is automatically added (enabled) to the workflow transitions based on his/her application level role and the workflow configurations for them. If "Static" this won't be done and no authorization will be granted concerning application level role workflow transition rights configuration when a new resource is added.
Show Short Description on Ticket Tab If enabled, the short description of the of the workflow is displayed in the form of the ticket(s) opened on it.
Related Ticket View Sets the view which is used in the Ticket form/tab of ticket(s).
Related Ticket Tab Preview Sets the view which is shown when the Ticket form/tab info of ticket(s) is activated.

The MANAGE SETTINGS FOR PROJECTS/SERVICES command allows to configure some settings for one or more project(s)/service(s) related to the workflow as those configured for a master project/service. Configurations which can be set separately are those defined for the master and concerning transitions (roles, resources and VCE conditions settings), outbound notifications (roles, resources), workflow notifications and MDMM definitions.

The EXPLORE WORKFLOW command allows to graphically explore how the workflow is configured as a results of its settings.

The EXPORT command allows to export the workflow settings for backup and/or later import. Specifically, the privileges configuration for workflow transitions are saved in an excel file for each workflow status.

Estratto da "http://wiki.itmsuite.eu/index.php?title=Workflow_configuration_steps_-_Creation_and_basic_settings&oldid=3268"