Conductor server and React.js

[Germs31]

HI. Am I allowed to hit the conductor server from a react application? is this good practice? Im under the impression that it should be hit from the backend. Can anyone give me in any insight? im pretty confused. please and thank you

Front-end -----> Back-end ------> Start Conductor

[aravindanr]

The Conductor UI is a react application that hits Conductor directly. So it's possible. @peterlau if you have any thoughts, please share.

[Germs31]

I can hit conductor server endpoints from my backend tho. sorry im a noob lol

[Germs31]

Conductor UI uses this endpoint when retrieving metadata workflows "/api/wfe/metadata/workflow". I was curious as to why it hits this because it is not an endpoint provided with in the documentation. @aravindanr

[peterlau]

That URL /api/wfe/* is associated with the legacy (2.x) UI. The latest conductor UI (V3.x) should be requesting from /api. In order to prevent CORS issues, we recommend setting up a reverse proxy of the conductor backend API to /api on the port & domain that is hosting the UI. This is done automatically (localhost:8080 -> localhost:5000/api) if you host the UI in debug mode using the yarn run start dev runner. The /docker directory of the repo also contains and example configuration for nginx.

[peterlau]

Alternatively, you can put the conductor server behind a CORS configured web server and modify plugins/fetch.js in the UI to fetch directly from your different-origin backend.

[Germs31]

@peterlau @aravindanr Thank you both so much! I will give these a try right away!

[v1r3n]

Hi,

Yes you can certainly call Conductor APIs from React backend.

Some potential reasons to do that:

1. Mark as task as completed in a workflow with human inputs (like approve expense and it marks the approval task as completed)
2. Start a new workflow, e.g when a user adds an item to the shopping cart, start a workflow to track the purchase flow