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
{{ message }}
This repository has been archived by the owner on Aug 26, 2022. It is now read-only.
We can add activation rules processing for entities, so we could assess whether a given entity should be activated (called) only if it meets the requirements proposed by the rules.
What should we change for this to work?
Add a rule evaluation engine (options: Drools, Retex, Ruler)
Add a CRD where the user can describe the rules in some kind of language/DSL.
Add the call to the rule evaluation engine to the message dispatching engine, passing the entity as an argument.
The text was updated successfully, but these errors were encountered:
Interesting option. This could even be "asked" and a function itself can evaluate to the result of the decision. This way any languages or stacks rule evaluation library can provide an implementation.
Interesting option. This could even be "asked" and a function itself can evaluate to the result of the decision. This way any languages or stacks rule evaluation library can provide an implementation.
Yes, we can provide it as an adapter.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is a feature proposal.
We can add activation rules processing for entities, so we could assess whether a given entity should be activated (called) only if it meets the requirements proposed by the rules.
What should we change for this to work?
The text was updated successfully, but these errors were encountered: