I ran into an issue while trying to trigger a workflow from within an App Builder page. Specifically, I encountered a CORS error because the App Builder’s origin URL isn’t whitelisted for the preflight check at rewst.engine.io . I was able to implement a workaround, but it required a fair bit of custom scripting. One of the ROC techs pointed me in the right direction by suggesting I could trigger a workflow by updating a label field and simulating a button click using JavaScript/HTML queries on the page. This worked for triggering the workflow, but I still had trouble getting the resulting data back into the HTML display. To resolve this, I added a MutationObserver to watch a button object (used as the output holder). Once the workflow returned and the button’s text was updated with new data, the observer inserted that data into the appropriate HTML block and then disconnected itself. This approach works well enough, and does give a bug if you execute the workflow again before it finished giving both field the same value as the first data back. But having native support for this kind of interaction between workflows and embedded app content would be incredibly helpful!
