Placing iLogic assemblies

[Anonymous]

I made an iLogic assembly which suppresses parts, changes parameters etc. by using a form. I want the assembly to be placed inside another assembly and after placement it should create a new assembly (by using the form) with all unsupressed parts in a sub folder.

In order to do this i thought of two options:- Using "Place ilogic component"

- Making a template file of the assembly

Place iLogic component

Whenever i use "place iLogic component" my own form does not pop up. Another kind of form pops up with all parameters in stead of my own form. I tried to overrule this form by using event triggers but this doesn't solve the problem. 

Another problem with the "place ilogic component": whenever i save the new created assembly, all parts get a suffix. Because of these suffixes my iLogic rules don't work anymore.

Making a template file of the assembly

If I press file -> new -> "my assembly" my form pops up and everything works fine. However when I press save it only saves the assembly and it leaves all parts inside the template folder. This is probably the way templates work but i'm trying to figure a way out where not only the assembly is saved in a new folder but also all unsupressed parts of the assembly.

My form (which doesn't pop up):

Wrong form:

[Anonymous]

Bump

[Anonymous]

Hi rdg,

The form that pops up is designed to link your top-level parameters to your iLogic assembly parameters.

If do not need them linked, press OK and place the assembly.  If you intend to make an iLogic assembly out of the new top-level you've created, you will need to link them.  Create the parameters in the top level first then place and select.  Alternatively, do it manually in a rule.

If you don't link, then you need to edit the form in the context of your iLogic sub-assembly.  I would suggest opening it in a new window rather than editing it in place, to avoid 'ThisDocument' or 'ActiveDocument' clashes.

With regards to numbering, the Place iLogic command automatically suffixes each component with -01, or the next increment.  In order to avoid this breaking your iLogic rules, you must always rename the browser node of any component that you wish to refer to via code.  This is good practice for all iLogic projects.  If you only wish to shorten the name, a further tip is to completely rename at least once.  Going from 'Part3' to 'Part' by deleting '3' can often result in Part3 manifesting itself again.  As an example, go from 'Part3' to 'Fish' then to 'Part' to ensure the desired shortened name sticks.

If you are referencing the actual filename then you can get around that by making the code interrogate the current name with

ThisDoc.FileName

If you wish for more control over file naming then use iLogic Design Copy first and place it as a new assembly.  If you are using Vault WG or Pro you can apply a Numbering Scheme to each component as it is copied.  If you intend to leave the filenames the same as the original I would advise against it.  Far too much potential for conflict.  A final option would be to write your own code that copies, renames, and replaces references.

Hope this helps.

Scott