Printed Forms form Relationships (ODT): Difference between revisions
From IHRIS Wiki
| Line 7: | Line 7: | ||
***content required scalar binary node. the binary ODT file. | ***content required scalar binary node. the binary ODT file. | ||
***name required scalar node. the name of the file when it is generated | ***name required scalar node. the name of the file when it is generated | ||
**segment_break. optional scalar node. what to use a a page/row break for the template. Defaults to <pre><text:p text:style-name="P1"/> | **segment_break. optional scalar node. what to use a a page/row break for the template. Defaults to <pre><text:p text:style-name="P1"/></pre> which is for a page break. For a line break it is <pre><text:line-break/></pre> | ||
You need to google for the others. | |||
To create the template_upload node, simply browse under magic data to /I2CE/page/$pageName/args, create a sub node template_file, do not set its type the select to load a binary file. | To create the template_upload node, simply browse under magic data to /I2CE/page/$pageName/args, create a sub node template_file, do not set its type the select to load a binary file. | ||
Revision as of 09:54, 12 April 2013
Magic Data
Under /I2CE/page/$pageName (or /modules/$modules/$pageName) you define:
- class(required scalar node) Value is "I2CE_PageGenerateRelationshipTemplate"
- args (parent node)
- relationship (required scalar node) = $relationship
- template_upload
- content required scalar binary node. the binary ODT file.
- name required scalar node. the name of the file when it is generated
- segment_break. optional scalar node. what to use a a page/row break for the template. Defaults to
<text:p text:style-name="P1"/>
which is for a page break. For a line break it is<text:line-break/>
You need to google for the others.
To create the template_upload node, simply browse under magic data to /I2CE/page/$pageName/args, create a sub node template_file, do not set its type the select to load a binary file.
