Solution Designer has been deprecated in favor of Opus Solution Environment (OSE).

Modify workflows

A solution's workflows define the lifecycle for object types in the data model. For example, an object type of directSupplierIncident could have a workflow that moves it from a state of Not Started to Under Investigation and then finally Completed.

Workflows fall into one of the following categories:

  • Base workflows, which are developed for specific base object types within the app. Solution Developers cannot modify or remove base workflows, but they can customize a base workflow by adding a sub-workflow.
  • Sub-workflows, which are added by a Solution Developer for customization purposes. Sub-workflows are built on top of base workflows, and Solution Developers can modify sub-workflows as needed.

An object type can have exactly one active workflow associated to it. An object type that is currently used with the solution uses the base workflow that it was developed with by default, or a Solution Developer can select to use a sub-workflow.

Select workflows for the solution

Workflows are one of the assets that solutions use, which means that they are added independently of a solution and can be reused across many solutions. Select workflows for an object type to determine which workflows the solution uses.

Workflows—with their associated states, transitions, conditions, and actions—can be shared across solutions within an environment, as long as the solutions are for the same app. Additionally, to use a workflow with a solution, the solution must also use the workflow's associated base object type or a sub-object type extended from that base object type. For example, Workflow X, which is associated to Object Type X, can be used by both Solution A and Solution B, as long as Solution A and Solution B are both for the same app and use Object Type X or one of its sub-object types.

Specify whether a specific object type that is currently used with the solution uses the base workflow that it was developed with or a sub-workflow extended from the base workflow. An object type can have exactly one active workflow associated to it.

  1. Select Customize in the side menu.
  2. Select Solutions.
  3. Select the Application with the solutions to view.
  4. Select the Action icon for the solution on the Installed Solutions tab.
  5. Select Edit.
  6. Select Workflow.

    Select Show Studios if the Workflow tab does not display.

  7. Select the Object Type to specify whether it uses its base workflow or a sub-workflow.

    The workflow currently in use with the object type displays:

    • Base Workflow displays if the object type is using its base workflow.
    • The sub-workflow name displays if the object type is using a sub-workflow.
  8. Select the Action icon.
  9. Select Connect.
  10. Select the base workflow or sub-workflow to use with the Object Type in the solution.
  11. Select Connect.

    The solution uses the selected workflow with the object type, and the workflow name displays.

Specify whether a specific object type that is currently used with the solution no longer uses a sub-workflow. Once disconnected, the object type reverts to using the base workflow.

  1. Select Customize in the side menu.
  2. Select Solutions.
  3. Select the Application with the solutions to view.
  4. Select the Action icon for the solution on the Installed Solutions tab.
  5. Select Edit.
  6. Select Workflow.

    Select Show Studios if the Workflow tab does not display.

  7. Select the Object Type that uses the sub-workflow you want to disconnect.

    The workflow currently in use with the object type displays:

    • Base Workflow displays if the object type is using its base workflow.
    • The sub-workflow name displays if the object type is using a sub-workflow.
  8. Select the Action icon.
  9. Select Disconnect.
    This action is only available if the workflow currently in use with the object type is a sub-workflow. You cannot disconnect a base workflow.
  10. Select Disconnect.
  11. Select Disconnect in the confirmation dialog.

    The solution no longer uses the selected sub-workflow with the Object Type, and Base Workflow displays.

Tips

Add sub-workflows

Add a new sub-workflow so that you can customize the workflow sub-states, transitions, transition actions, and transition conditions.

  1. Select Customize in the side menu.
  2. Select Solutions.
  3. Select the Application with the solutions to view.
  4. Select the Action icon for the solution on the Installed Solutions tab.
  5. Select Edit.
  6. Select Workflow.

    Select Show Studios if the Workflow tab does not display.

  7. Select the Object Type with the base workflow to extend the sub-workflow from.

    The workflow currently in use with the object type displays:

    • Base Workflow displays if the object type is using its base workflow.
    • The sub-workflow name displays if the object type is using a sub-workflow.
  8. Select the Action icon.
  9. Select Add.
  10. Enter a Sub-Workflow Name, which must be unique across all workflows for the Object Type in the environment.
  11. Select Add.

    The sub-workflow is added with the same base states as the base workflow it is extended from. The solution uses the sub-workflow with the Object Type and the sub-workflow name displays.

  1. Select Customize in the side menu.
  2. Select Solutions.
  3. Select the Application with the solutions to view.
  4. Select the Action icon for the solution on the Installed Solutions tab.
  5. Select Edit.
  6. Select Workflow.

    Select Show Studios if the Workflow tab does not display.

  7. Select the Object Type using the sub-workflow to copy.

    The workflow currently in use with the object type displays:

    • Base Workflow displays if the object type is using its base workflow.
    • The sub-workflow name displays if the object type is using a sub-workflow.
  8. Select the Action icon.
  9. Select Copy.
    This action is only available if the workflow currently in use with the object type is a sub-workflow. You cannot copy a base workflow.
  10. Enter a Sub-Workflow Name, which must be unique across all workflows for the Object Type in the environment.
  11. Select Add.

    The sub-workflow is added with the same states and transitions as the sub-workflow it is copied from. The solution uses the sub-workflow with the Object Type and the sub-workflow name displays.

Remove a sub-workflow from the solution when it is no longer needed. You can remove a sub-workflow even if it is in use by an object type.

Once removed, the sub-workflow (including its sub-states and transitions) is no longer available and cannot be recovered.
  1. Select Customize in the side menu.
  2. Select Solutions.
  3. Select the Application with the solutions to view.
  4. Select the Action icon for the solution on the Installed Solutions tab.
  5. Select Edit.
  6. Select Workflow.

    Select Show Studios if the Workflow tab does not display.

  7. Select the Action icon.
  8. Select Remove.
    The Remove Sub-Workflows panel displays all sub-workflows currently available in the solution, including those connected to an object type.

  9. Select the one or more sub-workflows to remove from the solution.

  10. Select Remove.
    The selected sub-workflows are removed from the solution. If a removed sub-workflow was in use by an object type, the object type automatically reverts to using its base workflow.

Modify a sub-workflow

Solution Developers can customize sub-workflows through custom sub-states, transitions, transition actions, and transition conditions.

  1. Select Customize in the side menu.
  2. Select Solutions.
  3. Select the Application with the solutions to view.
  4. Select the Action icon for the solution on the Installed Solutions tab.
  5. Select Edit.
  6. Select Workflow.

    Select Show Studios if the Workflow tab does not display.

  7. Select the Object Type with the sub-workflow to add a sub-state to. The States tab displays by default.

    The workflow currently in use with the object type displays:

    • Base Workflow displays if the object type is using its base workflow.
    • The sub-workflow name displays if the object type is using a sub-workflow.
    • Starting State – Indicates whether the state is the first state in the workflow.
      • Set as Starting State – The state is the first state in the workflow.
      • Not Set as Starting State – The state is not the first state in the workflow.

      Each workflow can have only one starting state.

    • State – The name of the state. Indicates whether the state is a base state or a sub-state.
  8. Select the Add Sub-State icon on the States tab.
  9. Fill in the following fields in the Add Sub-State panel:
    • Base State drop-down – Required. The base state to add the sub-state from.
    • Sub-State Name field – Required. The name for the new sub-state, which must be unique across all sub-states for the sub-workflow.
  10. Select Add.

    The sub-state is added and displays in the table.

Tips

  • Add transitions to position the sub-state between other states in the sub-workflow.
  • Set the starting state to define which base state or sub-state comes first in the sub-workflow.
  • Remove sub-states by selecting the Action icon for the sub-state and selecting Remove.
    Once removed, the sub-state is no longer available and cannot be recovered.
  1. Select Customize in the side menu.
  2. Select Solutions.
  3. Select the Application with the solutions to view.
  4. Select the Action icon for the solution on the Installed Solutions tab.
  5. Select Edit.
  6. Select Workflow.

    Select Show Studios if the Workflow tab does not display.

  7. Select the Object Type with the sub-workflow to add a transition to.

    The workflow currently in use with the object type displays:

    • Base Workflow displays if the object type is using its base workflow.
    • The sub-workflow name displays if the object type is using a sub-workflow.
  8. Select Transitions.
    • Transition – The name of the transition.
    • From State – The state that the transition moves from. Indicates whether the state is a base state or a sub-state.
    • To State – The state that the transition moves to. Indicates whether the state is a base state or a sub-state.
    • Condition – Indicates whether the transition has one or more conditions.
    • Action – Indicates whether the transition has one or more actions.
  9. Select the Add Transition icon.
  10. Fill in the following fields in the New Transition panel:
    • Transition Name field – Required. The name for the new transition, which must be unique across all transitions for the sub-workflow.
    • From State drop-down – Required. The state that the transition moves from.
    • To State drop-down – Required. The state that the transition moves to.

    Sub-state transitions must adhere to the same base state transitions from the base workflow.

  11. Select Add.

    The transition is added and displays in the table.

  12. If necessary, edit the transition to define conditions and actions.

Tips

  • Remove transitions by selecting the Action icon for the transition and selecting Remove.
    Once removed, the transition (including any defined conditions and actions) is no longer available and cannot be recovered.

Remove a transition from a sub-workflow when it is no longer needed.

Once removed, the transition (including any defined conditions and actions) is no longer available and cannot be recovered.
  1. Select Customize in the side menu.
  2. Select Solutions.
  3. Select the Application with the solutions to view.
  4. Select the Action icon for the solution on the Installed Solutions tab.
  5. Select Edit.
  6. Select Workflow.

    Select Show Studios if the Workflow tab does not display.

  7. Select the Object Type with the sub-workflow to add transition conditions and actions to.

    The workflow currently in use with the object type displays:

    • Base Workflow displays if the object type is using its base workflow.
    • The sub-workflow name displays if the object type is using a sub-workflow.
  8. Select Transitions.
    • Transition – The name of the transition.
    • From State – The state that the transition moves from. Indicates whether the state is a base state or a sub-state.
    • To State – The state that the transition moves to. Indicates whether the state is a base state or a sub-state.
    • Condition – Indicates whether the transition has one or more conditions.
    • Action – Indicates whether the transition has one or more actions.
  9. Select the Action icon for the transition to remove.
  10. Select Remove.
  11. Select Remove in the confirmation dialog.

    The transition, including any defined conditions and actions, is removed from the sub-workflow.

Set a workflow's Starting State to define which base state or sub-state comes first in the workflow. Only the original starting base state and sub-states added from it can be set as the starting state.

  1. Select Customize in the side menu.
  2. Select Solutions.
  3. Select the Application with the solutions to view.
  4. Select the Action icon for the solution on the Installed Solutions tab.
  5. Select Edit.
  6. Select Workflow.

    Select Show Studios if the Workflow tab does not display.

  7. Select the Object Type with the sub-workflow to set the starting state for.

    The workflow currently in use with the object type displays:

    • Base Workflow displays if the object type is using its base workflow.
    • The sub-workflow name displays if the object type is using a sub-workflow.

  8. Select States.

    • Starting State – Indicates whether the state is the first state in the workflow.
      • Set as Starting State – The state is the first state in the workflow.
      • Not Set as Starting State – The state is not the first state in the workflow.

      Each workflow can have only one starting state.

    • State – The name of the state. Indicates whether the state is a base state or a sub-state.
  9. Select the Make Starting State icon for the state to set as the starting state.

    The state is set as the workflow's starting state, and the icon in the Starting State column updates.