This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Introduction

Syncope uses a workflow concept to define transition task at different user states.

The aim of this page is to show how arbitrary workflow engines can be used within any Syncope project.

Implementation

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 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.

If you don't want to use a (full featured) workflow engine at all, you can also choose NoOpUserWorkflowAdapter as your Workflow adapter.

Deploy

Custom WorkflowAdapter implementation can be deployed:

  • at project definition time
    by adding own implementation into the overlay project, before to build Syncope.
  • at run-time
    by adding into the container classpath own implementation (container must be re-started to reload the classpath).
  • No labels