Global project linking vs. map external resources

[ax_skatz]

When it is appropriate to use the "global project linking" feature or the "map external resources" feature?
Scenario:
I have a template project that includes common items that may change over time. The template is stored in SVN (source control system).
Writers will add some or all of the common items to their own project.
When the content changes, writers will want to get the new common content and update the older version in their own project.

Is this scenario better suited for global project linking or mapping feature?

[NorthEast]

As the files would be created in and used by Flare projects, I would suggest using a project import (global project linking) instead of external resources, because:

- A project import is a lot more versatile, as you can specify the files to import based on types of file, conditions, or just by name.

- Flare will warn you if you try to edit imported files, and you cannot accidentally overwrite the original source. If you're not careful with external resources, you might synchronise (rather than import) and overwrite the original files.

- You have the option to automatically sync the files when you build a target.

[ax_skatz]

Thanks. This is a useful summary:-).