[MODWRKFLOW-1] Configure Workflow and Workflow-Engine Communication Created: 22/Dec/23  Updated: 06/Feb/24

Status: In Progress
Project: mod-workflow
Components: None
Affects versions: None
Fix versions: None

Type: Tech Debt Priority: P1
Reporter: Jeremy Huff Assignee: Kevin Day
Resolution: Unresolved Votes: 0
Labels: back-end, spike
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint: Aggies Sprint 1, Aggies Sprint 2
Story Points: 3
Development Team: Aggies
RCA Group: TBD

 Description   

Determine the appropriate communication paradigm between workflow and workflow engine, to ensure that all communication is handled through OKAPI.

Talking directly from mod-workflow to mod-camunda works when activating but when going through OKAPI this does not work and either 400s or 404s are returned. Why this is the case needs to be determined and the problem needs to be resolved.



 Comments   
Comment by Kevin Day [ 30/Jan/24 ]

This appears to have been resolved by improving error handling and fixing problems in the fw-cli program:

Comment by Kevin Day [ 31/Jan/24 ]

Additional problems have since been observed when performing the `fw run some_workflow`.
The error message is:
No suitable module found for path /rest/process-definition for tenant tamu
The problem is likely related to the configuration rest path.

Comment by Kevin Day [ 06/Feb/24 ]

Additional changes to the module descriptors is likely needed here.
The path structure may need to be changed.

Generated at Thu Feb 08 22:31:30 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.