[UXPROD-1050] Camunda PoC Created: 28/Aug/18  Updated: 27/Jun/19  Resolved: 24/May/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q4 2018

Type: Epic Priority: P3
Reporter: Jakub Skoczen Assignee: Peter Murray
Resolution: Done Votes: 0
Labels: NFR, automation_and_workflows, suppress-from-capplan
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-593 Workflow Services (Back End for Workf... Open
relates to UXPROD-600 Workflow App with To-Do App Integration In Review
Epic Name: Camunda PoC
Back End Estimate: XXL < 30 days
Estimation Notes and Assumptions: Timeboxed for 3 sprints
Start date (migrated):
End date:

 Description   

The TC proposes a 6-week PoC to gain practical, working knowledge integrating a workflow engine into FOLIO and implementing some real-world features. The PoC would target the Camunda workflow platform to implement a small set of features from the backlog.

In order to accurately understand pros/cons and design considerations for integrating Camunda with FOLIO, this PoC will assume that there is an intermediate integration mechanism with FOLIO’s API Gateway Okapi (akin to a mod-camunda). Note that this isn’t “Production-grade” integration, but, it is felt that we need some level of integration to validate what’s possible and to identify problematic or labor-intensive aspects should we pursue Camunda further.

The goals of the integration are two-fold. Firstly, for Camunda workflows to be able to react to events generated in FOLIO. Secondly, to be able to drive further functionality in FOLIO, or other third-party systems, from workflows executing in Camunda. Triggering events could be data flows or user interactions within FOLIO. For the purposes of the PoC the focus is on data flows. To maintain a separation-of-concerns, there is a desire to keep the workflow engine (i.e. Camunda) decoupled from Folio through the use of BPMN (Business Process Model and Notation) workflow definitions. The eventual development of workflow-related apps in Folio could be used to manipulate the BPMN contracts in order to make them more accessible for a broader, non-technical, audience.

From Workflow Proof-of-Concept Proposal

Important Documents

Background


Generated at Fri Feb 09 00:12:33 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.