Life Cycle Links

Life cycle links are links that target documents across sequences in the same application.

Life cycle links are automatically updated in the Ennov InSight link database to always point to the most current or specific version of a document in the application for published output. All life cycle linking in Ennov InSight is done through the Link Inspector.

Authoring Links

Life cycle links have three basic types: broken, stale, and historical.

— Broken links point to content that does not exist or has moved due to life cycle operations. They occur when a leaf is replaced in a new sequence with a new document, but that document's links are still targeting the old content and must be updated with new path information.

— Stale links are links where the source document and target document reside in different sequences, and Ennov InSight has not needed to update the link to insure a valid target during publishing. These links start in the old sequence targeting the current sequence. Any link marked as stale should be evaluated by the publisher for the correct target, because the target document may need to be operated on in the current sequence to resolve the link correctly, or you may need to verify that the historical target of the link is still valid for the reviewer.

— Historical links point from updated documents in newer sequences back to documents in old sequences.

Create In-Process Life Cycle Links

You can create life cycle links by targeting a link to a document that exists in an assembly outside the current assembly. This includes an assembly in any other sequence and is not restricted to the current application.

For historical in-process links pointing to a submitted sequence, you can target a leaf, a document or bookmark. To create historical links from a working assembly to previously submitted content, the target assembly must have been published prior to adding to life cycle. This sets the published output location on those leaf elements so that the appropriate relative path to the target may be determined.

Unless links are set to a document or a bookmark and any links targeting the old document get moved automatically to target the new document you assign under that leaf. The link is modified to point to the new location. In-process links created to a document or a bookmark will target to the location in previous sequence like it was selected when the link was created.

While links going to documents cannot target outside the current assembly/sequence, links going to leaf elements may target both old sequences and targets outside the current application. These links will have a status of Targeted even if the source document is not in the same assembly as the target document. They will be published as crossapplication links according to the same rules that govern reference leaf elements.

Reference Leafs and Hyperlinks Between Applications

You can link to content between different application lifecycles using reference leafs or hyperlinks. Links or references pointing to separate applications must navigate back to the root of the output, below the application number. For example, you might want to make reference to content in your IND application from your new NDA application by either reference links or hyperlinks, as shown in the following scenarios.

Reference Leafs

Any reference leaf can point to any other leaf in a separate application. The reference will navigate back to the root of the output under the application number. This example shows a target (Leaf 1) in a IND application that is referenced from Leaf 2 in the NDA application.

Life Cycle Links

*For the US, a 3-letter Application Prefix attribute is added to the application number.

In this example, the target document in the reference leaf is two levels removed from the root of the application.

— The navigation path of the href from Leaf 2 to Leaf 1 is: ..\..\ind123456\0000\m1\mydoc.pdf

— The navigation path of the href from Leaf 1 to Leaf 2 is: ..\..\nda234567\0001\m1\mydoc2.pdf

Hyperlinks

Any hyperlink can point to content in any other leaf in a separate application. The hyperlink will navigate back to the root of the output under the application number. This example shows a hyperlink target (in Leaf 1) in a IND application that is referenced from Leaf 2 in the NDA application.

*For the US, a 3-letter Application Prefix attribute is added to the application number.

In this example, the target document in the reference leaf is three levels removed from the root of the application. — The navigation path of the href from Leaf 2 to Leaf 1 is: ..\..\..\ind123456\0000\m1\test

\mydoc.pdf

— The navigation path of the href from Leaf 1 to Leaf 2 is: ..\..\nda234567\0001\m1\mydoc2.pdf