Capturing & Maintaining Workflows

Sub Banner

Having configured the Workflow App to establish a list of all workflow states (see Configuring States for use within Workflows) it is possible to start capturing and maintaining workflows.

Before starting this step a full set of workflow state mappings should have been identified (see Planning and Preparing for Workflow Configuration).

Configure the Workflow App

*Note: if you haven't already done so, before attempting to configure this App please familiarize yourself with the section of this manual describing the deployment and configuration of Apps.

This is achieved by configuring the Workflow App (3), so if not already using the configurator select the configure link (4) from within the CloudSET App Library to invoke it.

Create a New Workflow

If the workflow hasn't already been created select the "Add Workflow" button (1) to introduce a new workflow to the list (2), or if necessary drag an existing workflow to the "RUBBISH" bin (3) to remove from the list.

Enter Name of New Workflow

A dialog is presented requesting the name of the new workflow (1).

Enter a unique name and select the "OK" button (2) to create the workflow.

Identify which States are Involved in the Workflow

Once the workflow has been created it is presented in the list (1).

Expand the workflow element (2) and notice that all of the workflow states have been established as children (3), in addition to an empty or initial state (4).

Checking the corresponding box (5) will instruct the Workflow App to include a state within the list presented in the "WFStates" drop-down field when using the Ticket form (see See the Workflow in Operation).

If the box is left unchecked (6) then the corresponding state wont be present in the list and so the associated transition won't be relevant or possible for applicable Tickets.

*Note: it is possible to capture and maintain multiple workflows, each of which is applicable under different conditions (see Specify Conditions under which a Workflow Applies).

As such, some of the workflow states listed in the configurator are not applicable to all workflows, hence the option to include or exclude them.

Map the Order and Sequence of State Transitions

For each of the states involved in the work flow select all valid successor states resulting from the various transitions (1) and drag and drop each one on top of it's preceding state (2).

The state element in the workflow will be expanded and the successor state will be created as a child (3).

Each child state will be made available for selection in the "WFStates" drop-down via the Ticket form, when a Ticket is in the parent workflow state.

*Note: these mappings should have been identified during the planning and preparation of the workflow process (see Identify Workflow State Mappings in Planning and Preparing for Workflow Configuration).

If necessary a successor state can be removed as a child in the workflow by dragging and dropping onto the "RUBBISH" bin (4).

Map at Least One State to the Empty Value Step

Remember to map at least one possible state (1) to the empty value step (2) so it is possible to start the workflow by selecting an initial state from the drop down in the Ticket Form.

Once all workflow state mappings have been captured remember to save the workflow (3) to commit the configuration, otherwise updates will be lost when navigating away from the configurator.

The Save button will briefly change to display the text Saving... and any errors will be reported back in the dialog.

If no errors are reported, simply close the dialog (4), otherwise contact Coherence Design for support.

Close the dialog once the mappings have been saved (4).

 

Capturing & Maintaining Workflows

Sub Banner

Capturing & Maintaining Workflows

Having configured the Workflow App to establish a list of all workflow states (see Configuring States for use within Workflows) it is possible to start capturing and maintaining workflows.

Before starting this step a full set of workflow state mappings should have been identified (see Planning and Preparing for Workflow Configuration).

Configure the Workflow App

*Note: if you haven't already done so, before attempting to configure this App please familiarize yourself with the section of this manual describing the deployment and configuration of Apps.

This is achieved by configuring the Workflow App (3), so if not already using the configurator select the configure link (4) from within the CloudSET App Library to invoke it.

Create a New Workflow

If the workflow hasn't already been created select the "Add Workflow" button (1) to introduce a new workflow to the list (2), or if necessary drag an existing workflow to the "RUBBISH" bin (3) to remove from the list.

Enter Name of New Workflow

A dialog is presented requesting the name of the new workflow (1).

Enter a unique name and select the "OK" button (2) to create the workflow.

Identify which States are Involved in the Workflow

Once the workflow has been created it is presented in the list (1).

Expand the workflow element (2) and notice that all of the workflow states have been established as children (3), in addition to an empty or initial state (4).

Checking the corresponding box (5) will instruct the Workflow App to include a state within the list presented in the "WFStates" drop-down field when using the Ticket form (see See the Workflow in Operation).

If the box is left unchecked (6) then the corresponding state wont be present in the list and so the associated transition won't be relevant or possible for applicable Tickets.

*Note: it is possible to capture and maintain multiple workflows, each of which is applicable under different conditions (see Specify Conditions under which a Workflow Applies).

As such, some of the workflow states listed in the configurator are not applicable to all workflows, hence the option to include or exclude them.

Map the Order and Sequence of State Transitions

For each of the states involved in the work flow select all valid successor states resulting from the various transitions (1) and drag and drop each one on top of it's preceding state (2).

The state element in the workflow will be expanded and the successor state will be created as a child (3).

Each child state will be made available for selection in the "WFStates" drop-down via the Ticket form, when a Ticket is in the parent workflow state.

*Note: these mappings should have been identified during the planning and preparation of the workflow process (see Identify Workflow State Mappings in Planning and Preparing for Workflow Configuration).

If necessary a successor state can be removed as a child in the workflow by dragging and dropping onto the "RUBBISH" bin (4).

Map at Least One State to the Empty Value Step

Remember to map at least one possible state (1) to the empty value step (2) so it is possible to start the workflow by selecting an initial state from the drop down in the Ticket Form.

Once all workflow state mappings have been captured remember to save the workflow (3) to commit the configuration, otherwise updates will be lost when navigating away from the configurator.

The Save button will briefly change to display the text Saving... and any errors will be reported back in the dialog.

If no errors are reported, simply close the dialog (4), otherwise contact Coherence Design for support.

Close the dialog once the mappings have been saved (4).

 

Capturing & Maintaining Workflows

Sub Banner

Having configured the Workflow App to establish a list of all workflow states (see Configuring States for use within Workflows) it is possible to start capturing and maintaining workflows.

Before starting this step a full set of workflow state mappings should have been identified (see Planning and Preparing for Workflow Configuration).

Configure the Workflow App

*Note: if you haven't already done so, before attempting to configure this App please familiarize yourself with the section of this manual describing the deployment and configuration of Apps.

This is achieved by configuring the Workflow App (3), so if not already using the configurator select the configure link (4) from within the CloudSET App Library to invoke it.

Create a New Workflow

If the workflow hasn't already been created select the "Add Workflow" button (1) to introduce a new workflow to the list (2), or if necessary drag an existing workflow to the "RUBBISH" bin (3) to remove from the list.

Enter Name of New Workflow

A dialog is presented requesting the name of the new workflow (1).

Enter a unique name and select the "OK" button (2) to create the workflow.

Identify which States are Involved in the Workflow

Once the workflow has been created it is presented in the list (1).

Expand the workflow element (2) and notice that all of the workflow states have been established as children (3), in addition to an empty or initial state (4).

Checking the corresponding box (5) will instruct the Workflow App to include a state within the list presented in the "WFStates" drop-down field when using the Ticket form (see See the Workflow in Operation).

If the box is left unchecked (6) then the corresponding state wont be present in the list and so the associated transition won't be relevant or possible for applicable Tickets.

*Note: it is possible to capture and maintain multiple workflows, each of which is applicable under different conditions (see Specify Conditions under which a Workflow Applies).

As such, some of the workflow states listed in the configurator are not applicable to all workflows, hence the option to include or exclude them.

Map the Order and Sequence of State Transitions

For each of the states involved in the work flow select all valid successor states resulting from the various transitions (1) and drag and drop each one on top of it's preceding state (2).

The state element in the workflow will be expanded and the successor state will be created as a child (3).

Each child state will be made available for selection in the "WFStates" drop-down via the Ticket form, when a Ticket is in the parent workflow state.

*Note: these mappings should have been identified during the planning and preparation of the workflow process (see Identify Workflow State Mappings in Planning and Preparing for Workflow Configuration).

If necessary a successor state can be removed as a child in the workflow by dragging and dropping onto the "RUBBISH" bin (4).

Map at Least One State to the Empty Value Step

Remember to map at least one possible state (1) to the empty value step (2) so it is possible to start the workflow by selecting an initial state from the drop down in the Ticket Form.

Once all workflow state mappings have been captured remember to save the workflow (3) to commit the configuration, otherwise updates will be lost when navigating away from the configurator.

The Save button will briefly change to display the text Saving... and any errors will be reported back in the dialog.

If no errors are reported, simply close the dialog (4), otherwise contact Coherence Design for support.

Close the dialog once the mappings have been saved (4).

 

Capturing & Maintaining Workflows

Sub Banner

Capturing & Maintaining Workflows

Having configured the Workflow App to establish a list of all workflow states (see Configuring States for use within Workflows) it is possible to start capturing and maintaining workflows.

Before starting this step a full set of workflow state mappings should have been identified (see Planning and Preparing for Workflow Configuration).

Configure the Workflow App

*Note: if you haven't already done so, before attempting to configure this App please familiarize yourself with the section of this manual describing the deployment and configuration of Apps.

This is achieved by configuring the Workflow App (3), so if not already using the configurator select the configure link (4) from within the CloudSET App Library to invoke it.

Create a New Workflow

If the workflow hasn't already been created select the "Add Workflow" button (1) to introduce a new workflow to the list (2), or if necessary drag an existing workflow to the "RUBBISH" bin (3) to remove from the list.

Enter Name of New Workflow

A dialog is presented requesting the name of the new workflow (1).

Enter a unique name and select the "OK" button (2) to create the workflow.

Identify which States are Involved in the Workflow

Once the workflow has been created it is presented in the list (1).

Expand the workflow element (2) and notice that all of the workflow states have been established as children (3), in addition to an empty or initial state (4).

Checking the corresponding box (5) will instruct the Workflow App to include a state within the list presented in the "WFStates" drop-down field when using the Ticket form (see See the Workflow in Operation).

If the box is left unchecked (6) then the corresponding state wont be present in the list and so the associated transition won't be relevant or possible for applicable Tickets.

*Note: it is possible to capture and maintain multiple workflows, each of which is applicable under different conditions (see Specify Conditions under which a Workflow Applies).

As such, some of the workflow states listed in the configurator are not applicable to all workflows, hence the option to include or exclude them.

Map the Order and Sequence of State Transitions

For each of the states involved in the work flow select all valid successor states resulting from the various transitions (1) and drag and drop each one on top of it's preceding state (2).

The state element in the workflow will be expanded and the successor state will be created as a child (3).

Each child state will be made available for selection in the "WFStates" drop-down via the Ticket form, when a Ticket is in the parent workflow state.

*Note: these mappings should have been identified during the planning and preparation of the workflow process (see Identify Workflow State Mappings in Planning and Preparing for Workflow Configuration).

If necessary a successor state can be removed as a child in the workflow by dragging and dropping onto the "RUBBISH" bin (4).

Map at Least One State to the Empty Value Step

Remember to map at least one possible state (1) to the empty value step (2) so it is possible to start the workflow by selecting an initial state from the drop down in the Ticket Form.

Once all workflow state mappings have been captured remember to save the workflow (3) to commit the configuration, otherwise updates will be lost when navigating away from the configurator.

The Save button will briefly change to display the text Saving... and any errors will be reported back in the dialog.

If no errors are reported, simply close the dialog (4), otherwise contact Coherence Design for support.

Close the dialog once the mappings have been saved (4).