If a new parameter is installed on an Epic template and you want it on the copied template, where do you apply the update?

If a new parameter is installed on an Epic template and you want it on the copied template, where do you apply the update?

• A. Updates tab in the Template Manager
• B. Export changes to a file
• C. Open the original Epic template and copy manually
• D. Use the global search to apply changes

Answer: (A)

Centralized template maintenance and propagation of changes is what this tests. When a new parameter is added to a template, you want that change to appear in all downstream copies automatically. The Updates tab in the Template Manager is designed for this purpose: you apply the update once, and it propagates the new parameter to the copied templates, keeping everything aligned and avoiding manual rework. Exporting changes to a file is for moving changes between environments, not for applying updates to downstream templates. Opening the original template and copying manually creates a separate instance that won’t automatically receive future updates. Global search isn’t a mechanism for applying template updates.

Centralized template maintenance and propagation of changes is what this tests. When a new parameter is added to a template, you want that change to appear in all downstream copies automatically. The Updates tab in the Template Manager is designed for this purpose: you apply the update once, and it propagates the new parameter to the copied templates, keeping everything aligned and avoiding manual rework.

Exporting changes to a file is for moving changes between environments, not for applying updates to downstream templates. Opening the original template and copying manually creates a separate instance that won’t automatically receive future updates. Global search isn’t a mechanism for applying template updates.