Creating Lifecycle Workflows SampleManager Workflows

Scenario Projects (types) to manage samples Commercial (for the site owners) Regulatory (for the authorities) Controlled through components of a lifecycle Status values (based on Phrase list) Workflow States Workflow Action Type The scenario changes. It has been decided to associate samples with Projects, based on who has requested work. Projects will deal with specific requirements from the requesting organisation and must be controlled. They will follow a lifecycle (as do their samples). The lifecycle for projects is specific, using status values as shown here. These values are defined in a phrase list. To move from one status value to the next you must perform an action (to be defined), but you must only allow that action when the project is in a permitted state. These ‘permitted states’ are know as Workflow States and must de defined. In order for this to work you must consider how the lifecycle is constructed to match the scenario.

Scenario Lifecycle Action Types Status Values Workflow States The scenario is best viewed as a lifecycle. The requirements for the lifecycle have been described in previously and can be represented as shown here. Where I am =status value =Uppercase black text Actions that I can do =Workflow Action Types =White text on black background Before I perform the action =Workflow States =Grey bordered boxes In the workflow, Action 4: Re-start Work, Old status and status are swapped. Workflow States Generated or Progressing

Lifecycle Components Status values (based on Phrase list) Current & all possible situations Defined as source for the status field in the PROJECT_INFO table in structure.txt Workflow States Associated with PROJECT_INFO table Status values allowed before an action can happen e.g. Generated & Progressing Ξ 1 workflow state Workflow Action Type Action to move between status values Menu driven All components included in a Lifecycle Workflow are defined against a database table, in this case PROJECT_INFO. The phrase list id defined as the source of inputs to the Status & Oldstatus fields. The Action Types and Workflow States are associated with the table at definition and the status values that define the Workflow States must come from the phrase list. Multiple status values are allowed in any specific Workflow State.

Nodes Required Icon Node Icon Node Swap Property Set Property Copy Property Action From the Reference Guide: The Swap Properties node swaps the values of two properties of the current entity.

Workflow Created The lifecycle is created and is the definition of how the lifecycle will act. In this form it will do nothing. It must still be associated with the project entities even though it has been defined against that table. The way to do this is via an Entity Workflow. This is the topic of the next module.

Exercises Create a Lifecycle Workflow that satisfies all requirements shown here: