Trigger (external) iLoguic rule without putten every parameter inside

[gert-leonvanlier]

I would like to trigger an iLogic rule (internal or external) without writing every possible parameter that should trigger it. The event trigger is not working for this. Is there a way to trigger a rule after any parameter change and without writing every parameter inside the rule?

[WCrihfield · Accepted solution]

The "Any Model Parameter Change" Event Trigger, will only work with Model parameters.  It will not trigger when User parameters are changed.  So, the next options are the following:

• try using the "Part Geometry Change" Event Trigger instead, if that will work for your situation
• Set all your User parameters to "Export" (creates Custom iProperties for them, that will stay up to date with the parameter), then use the "iProperty Change" Event Trigger
• If using an external rule, you can create a local rule that simply contains a bunch of dummy variables, which are all set to = all the user (or other) parameters you want to trigger it, then just use a snippet to run the external rule.  Then any time one of those parameters changes, it will trigger that local rule to run, which will run your external rule.
• Create an Addin for your situation that will listen in the background for the parameter change event of those specific parameters in those specific files

[gert-leonvanlier]

See my remarks in bold:

@WCrihfield wrote:

The "Any Model Parameter Change" Event Trigger, will only work with Model parameters.  It will not trigger when User parameters are changed.  So, the next options are the following:

• try using the "Part Geometry Change" Event Trigger instead, if that will work for your situation
  It could work in some cases, but not all parameters are linked to geometry. But it would work in 80% of the cases I think.
• Set all your User parameters to "Export" (creates Custom iProperties for them, that will stay up to date with the parameter), then use the "iProperty Change" Event Trigger
  Preferably I do not want to do that (all parameters).
• If using an external rule, you can create a local rule that simply contains a bunch of dummy variables, which are all set to = all the user (or other) parameters you want to trigger it, then just use a snippet to run the external rule.  Then any time one of those parameters changes, it will trigger that local rule to run, which will run your external rule.
  I already use an internal rule to start the external rule, but I don't want to add every possible parameter to that rule to trigger the rule. It depends on the part and I don't want to maintain an internal rule just to trigger an external rule. That's the whole idea of using an external rule, in my opinion.
• Create an Addin for your situation that will listen in the background for the parameter change event of those specific parameters in those specific file
  Working on getting more knowledge of addins, but that would be something for the future.

---

I think the first option is the best for now and see how it will work. Starting an internal/external rule without putting every possible triggering parameter in a rule is too much to ask apparently.