...
| Div |
|---|
|
On this page| Table of Contents |
|---|
| maxLevel | 12 |
|---|
| exclude | On this page |
|---|
| type | flat |
|---|
| separator | | |
|---|
|
|
...
| Section |
|---|
| Column |
|---|
| Warning |
|---|
| If you continue to use legacy wiki markup, you must assign a unique id (see the id parameter) if there are more than one run macros on the same page. In this case, the default id generated in wiki mode is always 1 which only works correctly if only 1 run macro is on the page. Either convert the macros to rich text or add unique ids. |
|
|
Parameters
| Include Page |
|---|
| Run macro parameters |
|---|
| Run macro parameters |
|---|
|
Field Types
See Field types.
Advanced capabilities
...
- Horizontal radio button - gender:M:Gender:radio::M:Male:F:Female
- Single select with 12 lines - month:12:Month:select:12:1:Jan:2:Feb:3:Mar:4:Apr:5:May:6:Jun:7:July:8:Aug:9:Sept:10:Oct:11:Nov:12:Dec
- Checkbox (value same as text) - day::Day of$nbsp;week:checkbox-required:7:Sunday::Monday::Tuesday::Wednesday::Thursday::Friday::Saturday
Export
The html, representing the rendered body of the macro, can be exported to a page attachment or to the file system. This enables the dynamic content to be captured at a point in time for later viewing. An attachment or file created by this type of export, can be used on a page by including it in the body of an html macro. For example: {html:script=^bobs.html} {html}. If exportVersion=keep is used, the referenced attachment is already there, and the HTML macro is authorized for use on the page, then the macro body will not be rendered and the attachment will be included instead. This enables caching and automation capabilities.
...