Skip to main content
An automation that works on one project may depend on that project’s names, families, references or units.

​
1. List the dependencies

Record the source application, document type, required categories, families, templates, title blocks, units and linked files. Identify fixed element IDs or names that cannot identify the same target in another project.

​
2. Adapt a copy

Keep the working original. In a copy, replace project-specific inputs and explain what differs in the destination model. See Adapt an automation and Parameters.

​
3. Test both cases

Run one representative destination case, inspect the native result and check omissions. If the automation is intended to serve both projects, retest the original case too. Save the accepted version with its prerequisites; successful execution on one example does not establish general portability.