The content below is for Apache Syncope <= 1.2 - for later versions the Reference Guide is available. |
Syncope uses a workflow concept to define transition task at different user states.
You can choose within your workflow.properties file of your overlay project which workflow engine adapter should be used.
Syncope comes with a default ActivitiUserWorkflowAdapter implementation for Activiti BPM.
If you don't want to use a (full featured) workflow engine at all, you can also choose NoOpUserWorkflowAdapter as your workflow adapter.
If you want to attach a different workflow engine to your Syncope project, you need to provide an implementation of UserWorkflowAdapter interface. This can usually be done best by overriding (abstract) methods in AbstractUserWorkflowAdapter.
Syncope applies workflow concepts to both users and roles as transition task at different states.
You can choose within your workflow.properties file of your overlay project which workflow engine adapters should be used.
Syncope comes with a default ActivitiUserWorkflowAdapter implementation for Activiti BPM.
Not implemented yet.
If you don't want to use a (full featured) workflow engine at all, you can also choose NoOpUserWorkflowAdapter as your user workflow adapter.
The default choice is the NoOpRoleWorkflowAdapter.
If you want to attach a different workflow engine for users to your Syncope project, you need to provide an implementation of UserWorkflowAdapter interface. This can usually be done best by overriding (abstract) methods in AbstractUserWorkflowAdapter.
If you want to attach a different workflow engine for roles to your Syncope project, you need to provide an implementation of RoleWorkflowAdapter interface. This can usually be done best by overriding (abstract) methods in AbstractRoleWorkflowAdapter.