Transfer of Linked Documents

As an alternative to the general Transfer of Other Data, it is possible to enable propagation of Linked documents for a project. This allows the document name to be specified in a Design database, using a Link Description element (LNDESC) with a file URL and link propagation. Not all linked documents will be propagated; only those for which propagation has been explicitly enabled (attribute LNKPRP SEND).

This allows documents to be managed alongside the database to which they are linked. Linked documents will be transferred from the primary location of the database to secondary locations. Documents will only be copied if they are missing. Normally if a file is already present, it will not be overwritten, unless a command such as RECOVER is being used.

In order for a document to be propagated successfully, the specified folder must exist at the destination locations. For this reason, it is useful to store such documents in project-related folders, which are also likely exist at the satellite.

Linked documents will be transferred as a separate operation after the relevant Design database has been updated. Only missing files will be transferred.

In order for Linked documents to be transferred:-

• The project must have Linked document propagation enabled

• Linked Document propagation must not have been disabled for the Design database

• The Link description (LNDESC) must have LNKPRP SEND

• The Link URL must be a file URL ('file:///my_path_name') which references a valid file location

Linked documents will only be transferred as part of an update if a database update was required. There is a separate command to Synchronise Linked documents for a database. Linked documents will always be copied when a database is Allocated or Recovered.

House-keeping operations for Linked documents are not supported by Global. Thus if a database is deleted or de-allocated, its linked documents will not be tidied.