Creates child pages using a macro.
There is no visible content when used a in page. When the page is saved a new child page is created. This macro is useful for automatically generating hierarchies from templates.
User creates a new page using a template that has a 'create-child' macro in place. With the option 'render' set, that first template will actually generate two pages: one parent and one child.
The new page is called Colours and the template contains 5 'create-child' macros, each with a different page title: Red, Blue, Green, Yellow, Purple. The resulting pages will be:
The page title that should be used for the created page
The page where the child should be created, defaults to the current page
Only create the page once, if the page gets deleted, do not attempt to re-create it.
The template to use when creating the page (may be a space or global template, or a skin resource)
§ The pagename/templatename selectors are actually routing through a series of fall-back situations, the source for the template will first be checked against any editable-text objects with that name in the current space, then global editable-text, followed by a page in the current space with that name, then a space-template in the current space, after that a global template will be looked for and finally a builder resource with one of the extensions (.xml/.hxtml/raw/html/wiki) will be looked for and rendered appropriately dependant on the resource's extension.
NB: Confluence 'blueprints' (eg: Meeting Notes) are not accessible through the template parameter.
Whether to render the resultant page or not (so that create-child macros in the template can be executed)
A list of flags, one of which must be defined for the content to be displayed
A list of flags which must not be defined for the content to be displayed
Create a child page called 'Child'.