Camunda PoC (UXPROD-1050)

[UXPROD-1092] Provide for workflow callbacks into Okapi Created: 05/Sep/18  Updated: 16/Sep/20  Resolved: 18/Dec/18

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

Type: New Feature Priority: P3
Reporter: Peter Murray Assignee: Jeremy Warren
Resolution: Done Votes: 0
Labels: technical, workflow_poc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by UXPROD-1230 Establish pattern between Camunda nam... Closed
Epic Link: Camunda PoC
Analysis Estimate: Small < 3 days
Analysis Estimator: Peter Murray
Front End Estimator: Peter Murray
Front-End Confidence factor: Low
Back End Estimate: Medium < 5 days
Back End Estimator: Peter Murray
Rank: Chalmers (Impl Aut 2019): R4

 Description   

From Workflow Proof-of-Concept draft:

Camunda workflows may contain step(s) that require a callback into FOLIO, which would be executed via mod-camunda.

  • Depending on Camunda capabilities, options include: FOLIO Edge API calls; brokered callbacks (e.g. via a message queue); or even direct calls to Internal FOLIO APIs via Okapi
  • Camunda will preserve the FOLIO Tenant context of the triggering event
  • Camunda will comply with authentication and authorization access controls to FOLIO

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