Separate action expressions for different action triggers #161
Comments
snikolayev
added a commit
that referenced
this issue
Jun 3, 2018
- Add a notion of action triggers, that indicate how the activation was triggered (create, update, removal) - Ability to associate expressions with individual action triggers. Including expressions on action removals - Changed how linked facts are managed, to leverate action triggers - Tests
snikolayev
added a commit
that referenced
this issue
Jun 19, 2018
For backwards compatibility reasons, auto-retract linked facts at the end of fact propagation, instead of as part of "undo" action. This preserves existing observable behavior.
|
I need this feature for a demo of the product I'm building on NRules. Any rough idea of when they'll be ready? Do you have a preview available? |
|
You can clone the repo and build it yourself with pre-release code. There is no hard set date for the release |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add ability to tie different action expressions to different action triggers. I.e. a separate expression for newly created activations, vs updated activations. Also add ability to tie expressions with de-activations, effectively creating undo actions.
This also changes how linked facts are auto-retracted when activations are removed. Previously, linked facts were retracted immediately, as soon as the activation was removed. Now activation removals will get queued and deactivation expressions will get executed as part of rules firing, hence creating parity between insertion, update and removal of linked facts.
Existing
Doactions will continue to get executed on new activations and on updated activations.The text was updated successfully, but these errors were encountered: