Workflow Configuration
Configure Actionable Items (AI)		Configure ATS for Help

Workflow Configuration

Purpose

To create a new workflow configuration that ATS uses to move an Action through it's specific workflow.

Ats Workflow Configuration artifacts.

ATS uses four main artifacts to configure a workflow for use by a Team.

• Work Flow Definition specifies the states, their transitions and the state that represents the beginning of the workflow.
• Work Page Definition defines the a single state of the Work Flow Definition.
• Work Widget Definition defines a single widget and its corresponding attribute that the value will be stored in. It also provides some layout capabilities for that widget.
• Work Rule Definition defines certain rules that can be applied to Work Pages and Team Definitions.

How to do it

• Workflow Configuration
  • To create a new Workflow Configuration, use File->New->Other .. OSEE ATS->Workflow Configuration. Give the new workflow a namespace which reflects the relevant area and purpose and pick the most appropriate available starting workflow to base the new one on.
  • Workflows can be edited using the ATS Workflow Configuration Editor. States and their transitions can be edited through this interface. Other modifications will need to be edited through Work Flow Definition attributes and relations.
  • State changes can also be edited directly by opening the Workflow Definition with the Artifact Editor. "Transition" is a multi-valued attribute which is used to define the available transitions between states. Transitions take the form <SourceState>;<Transition>;<DestinationState>
  • Available transitions are:
    • ToPage
    • ToPageAsDefault
    • ToPageAsReturn
  • A new transition is created by adding a new value to the attribute using the green + to the right of "Transition" and an existing transition is deleted using the red x to the right of it.
  • States in the transition list must exist as Work Pages named with the following syntax: <WorkflowDefinitionName>.<NameOfState>
    • e.g. osee.ats.CustReqWorkflow contains a transition "Endorse;ToPage;Cancelled" so Work Pages osee.ats.CustReqWorkflow.Endorse and osee.ats.CustReqWorkflow.Cancelled must exist or an exception will be generated when opening the Workflow Definition in the Workflow Configuration Editor.
  • Do not make changes using the Artifact Editor and the Workflow Configuration Editor in the same editing session or OSEE may become confused as to which state is which.
• Work Pages, Widgets and Rules are currently edited through the attributes and relations using the default Artifact Editor. See links above to set the proper values.
• Configurations can also be created through the java. An example of this can be seen by looking at the org.eclipse.osee.ats.config.demo plugin. This plugin, and the DemoDatabaseConfig.java class, shows how to programatically generate work flows, pages, rules and widgets to configure ATS. This configuration will be generated during a database initialization.

Configure Actionable Items (AI)		Configure ATS for Help