About Transitions

Transitions are used to:
  • Submit new primary items.
  • Move primary items to a different state.
  • Update existing items.
  • Delete items.

Most transitions are available as buttons on state forms. Users click a transition button to initiate the transition. In most cases, users can enter data about an item on a transition form before completing the transition.

You can replace a transition button with a button, hyperlink, or image control that can be placed anywhere on the form. For button and hypertext controls, you either use the transition name as the control label, or type a different name. For examples, see Custom Transition Control Tutorials.

Transitions can also be executed without user intervention. For example, you can:

  • Create actions that execute a transition based on the value of a specific field. For details, refer to About Actions.
  • Create a notification that transitions items based on a rule you define. This task is performed in Application Administrator. For details, refer to the SBM Application Administrator Guide.
  • Use the SBM Application Engine Web Services API, along with transition actions. For details, refer to the Web Services Developer's Guide or Web Services Developer's Guide.

Transition Types

A variety of transition types are available. Regular transitions are the most commonly used transition type because they move items from one state to another.

Other transition types post items into different workflows or applications or copy items. For details, refer to Transition Reference.

Related Topics

Transition Types

Adding a Transition