About Copying Designs with iLogic Rules

Use iLogic Design Copy to copy a design containing iLogic rules.

iLogic Design Copy addresses the special considerations when copying an iLogic-enabled design template.

Note: You can use iLogic Design Copy even if your documents do not involve iLogic rules.

Workflow 1: Using Configure First

Use Configure first if:

• The copy is intended as a fixed configuration and does not need the rules.
• You do not want to edit the rules on the copy.

1. Load the iLogic Design Template.
2. Define a new configuration by changing input values and firing rules.
3. Save the iLogic Design Template.
4. Run iLogic Design Copy to create a copy of the design template saved in the desired configuration state.

Workflow 2: Using Copy First

Use Copy first if:

• You intend to change the rules or make other changes after copying to create a new, similar iLogic template.
• You do not want to change the original design or template.

1. Run iLogic Design Copy to create a copy of the iLogic Design Template.
2. Load the copied design template.
3. Define a new configuration by changing input values and firing rules.
4. Save the copied design template.

About Renaming Files

It’s a good idea to rename the files to avoid overwriting existing files or creating duplicates in the destination folder. Duplicate filenames in a project can lead to use of the wrong file when an assembly is loaded.

In the iLogic design template being copied, write rules that reference files renamed during the copy operation to account for a variable filename, such as Component.Replace ("part:1", prefix_var & filename & suffix_var). Otherwise, edit the rules by hand and change the filenames.

Be sure that all component browser names in the source assembly documents are stable before copying while using the renaming options. By default, component browser names are linked to the filenames they point to in Inventor. When a filename changes, the browser name follows suit. To break this link, rename the component browser to something user-defined. Once the browser name is out of sync with the filename, the link is broken and the filename no longer drives it. If this link is not broken, and the copied document is renamed during the copy operation, rules that refer to component browser names fail.