Documents and Libraries
You can create documents in a library just like you do in a model.
When a document is created, the var-tags and block-tags are processed in the current model or library. So the tag <block switch=“main.info.source”> will check the graph main, node info and data source of the current library or model.
External information in the document
Sometimes it is a great solution to use information of a library in a document created in the main model or other library. The only way to get information needed of a var or block tag is to copy that information in the model creating the document. You can do this by getting the information out of the library using the libgraphout node, see libraries.
For text fragments, this is not the case. Each text fragment you create, is stored on a list, which is approachable for the document generator. This means, if you create a text fragment hello in a library, you can use that fragment in a document created in the main model or another library. So be aware, using hello in the main model or other library will accumulate the text (if the iteration is the same).
Getting documentlink from a library
If you have created a document in a library, you can offer the link to the user from the calling model. This is done as follows:
In the library where you have created the document, go to the node libgraphout, and press the button
[Lib. comm.] on
Here you can give the output data a name (in the example reportlink), and select the data generated_<reportname> in the node where the document is created.
The data generated_<reportname>, in the example reportx, holds the internal filename to the end result. Normally, you do not see that in the Actions screen, where it is hidden for the user.
In the calling model of the library, the value is automatically given back. Here you can use that value in a link, like this;
In this example the value given back is in the node calltolib and was called reportlink.