So this is either going to be a really stupid question (new to Camunda) or, I am hoping, there are some examples or best practices someone can point me to - since I’ve struck out on massive Googling!
I am evaluating Camunda as the BPM engine for a massive web app. The app has all the normal stuff you’d expect… users move from one page to another, hit re-load or back button, some pages auto-refresh, there are lots of graphs and dashboards that update independently while the page is open. The app is very rich in style, graphics, blah blah.
A lot (but not all) of what the App does is basic workflow/BPM type work. We’d like to replace the home-brew workflow since it’s getting pretty nasty to manage!
What I am trying to do is use Rest calls from the front-end (AngularJS) to start and stop Camunda processes AND get data back from Camunda into the AngularJS code (so it can update dashboards, for example).
All I have found on the web is how to embed Angular (forms) in Camunda. With respect to forms, for example, I could not find a way to get the data from a Camunda task back to Angular front-end, when the front-end code posted a call to start a Camunda process. For example, a login screen, where I could call a Camunda login verification process and send a “Yes” or “No” to the front-end.
The question is:
- Am I approaching this the wrong way? (entirely possible)
- If so, are there any “best practices” or “design patterns” out there to address this type of use case?
Thank you, one and all, for any guidance.