You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So users can chain together actions! e.g. when a pub successfully gets a DOI, it moves on to a "ready to publish" stage.
So users can run actions in a stage in order -- e.g. first pull from airtable, then pull from google drive (could also do this with moves, but would need to trigger moves)
Requirements
New labels on all action rule dialogues to clarify what each dropdown is selecting
Two new event types in action rules: "When an action runs successfully..." and "When an action fails..."
When one is selected, a new dropdown labeled "Action" appears that allows users choose from a list of configured actions in that stage that, when run, will cause the selected action to run
Once configured, rule runs selected action when another action has succeeded or failed
Warn the user if there is an infinite loop in the same stage and prevent them from creating the trigger
Acceptance Criteria
Two new rules and corresponding Events should be added for the "action run succeeded" and "action run failed" events.
Each new rule should have an additional configuration that specifies the action instance to observe for successes/failures.
To prevent loops, action that triggered and triggered action cannot be the same
Mockups (if available)
The text was updated successfully, but these errors were encountered:
I know, I know, controversial, but we're getting a lot of requests for some way of doing this — can also see using field updates as a way to do this, but this seems a little simpler, especially because not all actions have great field-writing capability.
When that action has a successful run on a pub, the next action is triggered. If the action runs but fails, no action is run.
I could also see a version that's just "when an action runs..." and has the ability to set an action to run for "when it succeeds" and "when it fails"
We could also restrict this to moving stages rather than allowing all actions to be run as a result of the trigger to keep it more constrained (although that's less cool!).
Motivation
So users can chain together actions! e.g. when a pub successfully gets a DOI, it moves on to a "ready to publish" stage.
So users can run actions in a stage in order -- e.g. first pull from airtable, then pull from google drive (could also do this with moves, but would need to trigger moves)
Requirements
Acceptance Criteria
Event
s should be added for the "action run succeeded" and "action run failed" events.Mockups (if available)
The text was updated successfully, but these errors were encountered: