Is it possible to execute iLogic of components when placing components in assemblies?

[seosk1571C4FHH]

Is it possible to run iLogic that belongs to a component when placing a component in an assembly?

[WCrihfield]

Hi @seosk1571C4FHH.  This does sound possible.  Why would you want to do this?  What are you wanting the iLogic to do at this point in time, and what should it be acting upon?  If this were possible, then how you specify which document each line of your iLogic code is supposed to be focused on will become critical, because there will be multiple document references involved.  The main assembly document that is showing on your screen at that time will remain the 'active' document in this situation.

There is also a property within every iLogic Form, below the 'Behavior' properties heading, named "Show on Place Component", with a True/False type value.  Not sure how that works when it is a 'global' iLogicForm, but when it is an 'internal' iLogicForm, the Form is saved directly within an Inventor Document, so it would show when that specific document reference is placed into an assembly, as an assembly component occurrence.

Just to add to what I said before about this being possible...I believe that we should be able to 'monitor/listen' for the AssemblyEvents.OnNewOccurrence Event, which gets triggered both before and after this type of event.  When using that event handler, we are provided with a reference to the AssemblyDocument that the ComponentOccurrence is being added to.  We are also provided with a reference to the ComponentOccurrence object itself, but only during the 'after' timing state of the event.  And usually within the 'Context' is an entry named "ComponentDefiniion", which contains a reference to the ComponentDefinition object that the new ComponentOccurrence object will be (or is) referencing.  That ComponentDefinition is usually provided even during the 'before' timing state of the event (before the ComponentOccurrence has been added into the assembly).  However, keep in mind that this event is triggered every single time any component is added to any assembly, for as long as Inventor is running.  So, the custom code you put inside that event handler will most likely need to do some filtering, as efficiently as possible.  I assume you will only want this to act upon specific model documents, which have specifically named rules or forms saved within them.

[seosk1571C4FHH]

We customize and use both ends of PFA VALVE after cutting and add air fittings that control VALVE. To meet these two conditions, we try to use iassembly + ipart at the same time, but when we add ipart to iassembly and use it, there is a problem that the user's dimension cannot be entered. So, when adding the valve iassembly without using the cutting dimension as ipart, I plan to run iLogic to generate a dialog window and reflect the user dimension after inputting it.