Resource output connector

Resource output connector
The Resource output connector stores output as resources in the runtime repository. The stored resources can be accessed from, for example, Template Engine, SMTP (MIME) connector and MIMEAddPart script function.
For example, a StoryTeller document can be stored as a resource via a Resource output connector, and this resource can then be wrapped into the output from a Template Engine Process.
Platform settings
Yes – Use Duration and Time unit below to specify for how long to store the resource in the runtime repository.
No – Do not set an expiry time for the resource.
The number of <Time units> to store the resource.
Runtime settings
Resource connector and Resource filter
You can use a Resource output connector or a Resource filter (see Resource filter in the Design Center documentation) to store output as resources in the runtime repository. For example, you can use the connector if you only want to store the output as resources, and use the filter if you want to deliver output via a standard output connector and driver (e.g. a File connector and PDF driver) and at the same time store the output as resources.
Accessing stored resources
A resource stored in the runtime repository can be accessed by referencing the GUID or name of the resource. The following types of URIs can be used to access a resource:
For example, Template Engine can use the #include directive to include the resource in the output:
#include('resource://name=my_text')
 
OpenText StreamServe 5.6.2 Updated: 2018-01-26