Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transition Actions in Configuration #3

Open
kohsah opened this issue May 30, 2018 · 0 comments
Open

Transition Actions in Configuration #3

kohsah opened this issue May 30, 2018 · 0 comments

Comments

@kohsah
Copy link
Contributor

kohsah commented May 30, 2018

A transit moves a document from one state to another. Typically we want to execute code when that happens. Currently this is done on the back-end system by matching the transition name and executing some code on the basis of that. Which implies hard-coding transition names in code.

This aspect could be factored into configuration - by having a "post-transition-action" property which invokes a specific named API provided in the configuration. e.g.

"postTransitionAction":  "customFuncton"

customFunction is an API exported by a recognized module (also named int the configuration

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant