||
Skip to end of metadata
Go to start of metadata

Workflow extensions allow you to attach a custom workflow to various operations in the App Manager such as user signup, Web application publishing, and subscription etc. By default, the App Manager workflows have Simple Workflow Executor engaged in them. The Simple Workflow Executor carries out an operation without any intervention by a workflow admin. For example, when you subscribe to a Web application, the Simple Workflow Executor allows you to subscribe to it without the approval of the admin.

If you need to enforce intervention by a workflow admin, you can engage the  WS Workflow Executor . It invokes an external Web service when executing a workflow, and completes the process based on the output of the Web service. For example, when you subscribe to a Web  application, the request goes into an intermediary state where it remains until authorized by a workflow admin.

By default, the WS Workflow Executor comes with,

  • A sample BPEL and Human Task for each standard workflow such as publish-application, subscription-creation and user-signup. You can also customize the default implementations.
  • A Jaggery-based Web application named admin-dashboard (https://<AppM_HOST>:<AppM_PORT>/admin-dashboard). It provides a GUI for the workflow admin to approve/reject pending Human Tasks. 

When executing a workflow, an entry is added to the  APM_WORKFLOWS table in the App Manager database, indicating the workflow status and workflow external reference along with other information. This entry is used to track the progress of the workflow throughout its lifecycle. At a given time, the status of a workflow can be  CREATED APPROVED   or  REJECTED CREATED is the default status of a workflow. It gets promoted to  APPROVED or  REJECTED , based on the response from the workflow engine.

Workflow extensions in WSO2 App Manager help attaching a workflow to the following operations.

  • No labels