• Camunda PoC
    • XXL < 30 days
    • Timeboxed for 3 sprints


      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


      TestRail: Results


          Issue Links



                peter Peter Murray
                jakub Jakub Skoczen
                0 Vote for this issue
                6 Start watching this issue



                  TestRail: Runs

                    TestRail: Cases