Meta data

Along with the result document, ITP/OnLine Server writes a meta data xml file at the end of the model run. This meta data file is available in the ProcessResult.dss exit point script. This script, which may be modified as part of ITP/OnLine customization, refers to the meta data file through its MetaData parameter. The meta data consists of three sections:

For every editable Text Block question, its result will end up in an itp:user-textblock node inside the itp:forms section. It will be identified by an id attribute and it will contain an itp:content subnode that holds the actual Text Block information.

Other parts of the xml will refer to the Text Block content by using the value of the id attribute. E.g. the FORM example mentioned above would end up in the itp:forms section as follows:

<itp:form>
	<itp:name>A form with a single editable text block</itp:name>
	<itp:element>
		<itp:key>Clause A001</itp:key>
		<itp:id> A001</itp:id>
		<itp:value>user:01c86735f934361b00000e70.1</itp:value>
	</itp:element>
</itp:form>
<itp:user-textblock id="user:01c86735f934361b00000e70.1">
	<itp:content>&lt;textblock&gt;&lt;content&gt;&lt;tbk xsv="2.0.1"&gt;&lt;par font="header" indentation="0" hanging-indentation="false"&gt;&lt;txt bold="false" italic="false" underline="false" id=""&gt;&lt;![CDATA[Clause A001]]&gt;&lt;/txt&gt;&lt;/par&gt;&lt;par font="normal" indentation="0" hanging-indentation="false"&gt;&lt;txt bold="false" italic="false" underline="false" id=""&gt;&lt;![CDATA[Any damages that are the consequence of terrorism are explicitly excluded and will not be covered by this policy.]]&gt;&lt;/txt&gt;&lt;/par&gt;&lt;/tbk&gt;&lt;/content&gt;&lt;fieldset&gt;Customer&lt;/fieldset&gt;&lt;fieldset&gt;Policy&lt;/fieldset&gt;&lt;/textblock&gt;</itp:content>
</itp:user-textblock>