Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Note
titleVersion Warning

The content below is for Apache Syncope <= 1.2 - for later versions the Reference Guide is available.

The user workflow in Syncope describes and manages the identity lifecycle workflow describe and manage the identity lifecicle.

It consists of a sequence of concatenated steps describing actions and user interactions connected to the identity management process (BPMN 2.0). This aspect makes the whole system very flexible to adapt to different situations. Take a look at customize workflow definition to find out how you can provide your own custom workflow behavior.

Syncope User workflow drives:

  • user transition status;
  • notifications;
  • approval requests;
  • action/operation availability (like creations, updates, deletion about identities);
  • and other (eventual) custom action executions.

Managing roles also inside a workflow is currently not supported, but planed for a future release (see SYNCOPE-173)

Workflow The workflow engine is a pluggable aspect of Apache Syncope: this lets every deployment choose among one of provided engine implementations or define new, custom ones.
Default The implementation selected by default is based on Activiti BPM: see Choose workflow engine for more information on how to select a different workflow engine.

Default Workflow

Image Removed

Yellow processes represent (Java) service tasks, whereas green and blue highlighted processes are waiting for a user interaction.

Samples

Take a look at some workflow examples, to get a better understanding of how this feature can be used within Syncope.

Children Display
sorttitle
The default workflow supports user approval for self registered users, as well as a token validation. Active users can be updated, whereas suspended (inactive) users can only be deleted or reactivated.
To achieve any other behavior you need to modify your workflow definition. By doing this you can for example easily disable auto activation for new users, or call your own service task implementation.