Event Triggers Remove Tabs for Users

[jwente123]

We recently updated to Inventor 2018 from 2015.

I noticed that the event triggers for ilogic now have tabs for All Documents, Parts, Assemblies, Drawings, This Document.

Is there a way to block users from certain tabs or remove these tabs, I only want them to have access to this document.

Which would be similar to the way it was. You could make changes to the part you are working in, or you had to make changes to the template for new parts.

Now if someone mistakenly adds a rule to the part tab instead of This Document tab, it adds this rule to every part in our system and overrides our template for new parts.

Potentially a nightmare scenario depending on what the rule is.

Does anyone else have this issue or have a way to resolve it.

Thanks,

[jhackney1972]

I fail to see your issue.  If you notice all the iLogic Event Trigger tabs, except "This Document" only allow you to set an event trigger for an External Rule.  The "This Document" tab will allow you to set an event trigger for the current document no matter the type.  If you set it in one particular part file, it will not be available to other part files in your database.  If you set up a rule in an Inventor template, and set an event trigger for it, it will affect any model or drawing created with the template and only that file not others in your database.

An iLogic rule will only be applied to the file it is included in.  If you do not want it to affect all new files, keep it out of your templates.  iLogic rules will not automatically propagate from one file to another in your database no matter what triggers you set.  If the iLogic routine is in the file and a trigger exists it will fire not affecting other saved files. 

[mcgyvr]

---

@jhackney1972 wrote:

If you set it in one particular part file, it will not be available to other part files in your database.  

An iLogic rule will only be applied to the file it is included in.  If you do not want it to affect all new files, keep it out of your templates.  iLogic rules will not automatically propagate from one file to another in your database no matter what triggers you set.  If the iLogic routine is in the file and a trigger exists it will fire not affecting other saved files. 

---

@jhackney1972 

Thats not true anymore from what I can tell.....

I can create a new external rule.. go to the "parts" tab of the trigger dialog and select it to run "after save" and it will run on ANY part I open after that.. and to be clear I am NOT creating this rule in a template at all.. 

Its dangerous...

Now I'm not sure if that trigger is only valid for my computer and won't effect other users as I'm only by myself here and can't try it..

But the new trigger dialog can certainly cause rules to run in files that did not have them in there before..

[mcgyvr]

And to add to all this..

Once my evil coworker on his last day creates this rule and sets it to run on all parts how do I find out which part he created that rule in to clean up the mess they made.. All my part files and assembly files now say "go F yourself" both in a message box and in speaking voice on my speakers whenever we save a part.... 

I can likely search for the external ilogic rules on their computer and hopefully get lucky there and delete it but won't Inventor then error out because the rule file cannot be found?

wow.. surely something must be missing here from my assumptions. There has to be some security here..

It must be specific to one computer only or something.. 

I'm so curious now.. 

[jwente123]

If one user triggers an external rule to run in all parts, it affects all of our users.

We have an external rule that will auto populate the description with the max dimensions of the part (LxWxH) before save.

We use the rule for old parts that get copied from past designs, if a user mistakenly triggers this rule on the parts tab instead of on this document tab, (that is user error but still a likely possibility to happen), this then turns on this rule for all parts for all users. Then if someone opens an assembly, and saves the parts, unknowing to them they just over written every part description.

[Curtis_Waguespack]

@MjDeck , 

Hi Mike,

Can you take a look at this and let us know if there is a way to lock this down a bit.

@jwente123,

I have a rule that will delete the event triggers in a file, and then copy the event triggers from our template file of the same file type, so that all of our files behave the same. We have this rule piggybacking off of another rule that the users are sure to run. 

We did this precisely because there wasn't a way to run a rule on all parts, all assemblies, etc. So i'm wondering if having a "scrub event triggers" rule set up to make sure no extra "All Parts" triggers make it into you files would help you.

We're still using 2017 and have only kicked the tires on 2018, but I'll have to figure this out in the coming months as well.

I hope this helps.
Best of luck to you in all of your Inventor pursuits,
Curtis
http://inventortrenches.blogspot.com

[jwente123]

A "scrub event trigger" rule would at least give a layer of protection from accidental misplaced triggers.

[Curtis_Waguespack]

---

@jwente123 wrote:

A "scrub event trigger" rule would at least give a layer of protection from accidental misplaced triggers.

---

Hi jeffwente5345,

See this link:

https://forums.autodesk.com/t5/inventor-customization/updating-old-drawings-with-ilogic-rules/m-p/65...

[MjDeck]

Inventor 2018.1 and later has support for event-triggered rules that run in all documents. This allows you to standardize without having to copy event triggers from document to document. If your External Rules directory is on a network share, then changes by one user can affect all others who are using that network share. To reduce the risk, here's a few ideas:

- If there are users who should never modify those triggers, you can use Windows permission settings to deny them write access to that folder. Or you could deny them write access to the specific file (RulesOnEvents.xml) that contains the event triggers. (Setting permissions on the folder would also have been a good practice before the "all documents" event triggers were available. If you don't want a user to modify the event triggers, then you probably don't want them to modify the rules either.)

- Suppose you're a user who is authorized to work on the triggers, but you're still in the development and testing stage. To avoid impacting other users, the best thing would be to change your External Rules directory to a folder on your machine rather than the network share. Copy the external rules and RulesOnEvents.xml from the network share to your machine and edit them there. When you're finished, copy your changes back to the network share.

- That method could be used to defend against changes that other users might make. If you're running from a local copy instead of the network share, then you have complete control over the event triggers that run on your machine.