Can one workflow change the isActive (enable/disable) trigger value of another workflow?
Context: We're trying to allow users to disable/enable a workflow without giving them rights to modify the workflow.
Need: It's more of a protective step, because the users didn't build the workflow nor do they understand how workflows work, but when they need to enable/disable the workflow we build for them we don't want them to have to engage our team, just to get us to manually enable/disable the workflow. Once enabled, the trigger is set to run on a cron schedule.
We're trying to mitigate the risk while still allowing them some ability to enable/disable the workflow. If we can do this by allowing the users to use a front-end app that will execute an on-demand controller workflow, we're hoping to toggle the isActive status of their workflow trigger. This access will be driven by a front-end (dynatrace app) and handle everything via code.
I know how to read data from workflows (status, execution lists, errors, configurations etc). What I'm trying to understand with more clarity is what the scopes below provide and what limitations are in place (both in the UI and within the Automation Engine APIs).
- automation:workflows:write (Allows creation, updating, and deletion).
- automation:workflows:run (Allows manual triggering).
Our current attempts to do this directly against the workflow led us to this error from the API:
[
{
"error": "Dynatrace workflow lookup failed (403): <html><body><h1>403 Forbidden</h1>\nRequest forbidden by administrative rules.\n</body></html>\n"
},
500
]
