This pane is only visible when a clause is selected. As an exception to the other tabs of the Assemble Document mode, the actions in this tab only apply to the selected clause.
At first glance, several of the options available in this pane — such as visibility, numbering, custom styling, etc. — may seem to overlap with the settings available in the edit pane, so you may be wondering which one to choose.
The difference between changing those settings in the edit pane or changing them in the advanced pane, is that changes made in the advanced pane apply only to the selected instance of the clause. Anything you change in the advanced pane, will not have any impact whatsoever on other instances of the same clause in your document, or other instances of the clause in other documents.
Note that this difference is only relevant for library clauses. Any instance of an adhoc clause is always unique — i.e., there cannot be two instances of the same adhoc clause.
Make clause invisible
The option allows you to temporily hide a clause (and its children). The effect is similar to checking the option in the enabled? part of a clause.
If the invisible clauses option is checked in the visibility options (see the popup-list accessible through the button at the right side of the screen), the clause will nevertheless be visible, but redlined.
Show clause title?
The checkbox allows you to toggle the visibility of the optional title of the selected clause’s instance. Toggling this checkbox is identical to toggling the button in the operations toolbar.
This checkbox will be hidden when no title is available in the selected clause.
Hide all numbering
The checkbox allows you to hide all the numbering in the selected clause instance and its descendant clause instances. Toggling this checkbox is identical to toggling the button in the operations toolbar.
When you enable this checkbox, a secondary option will become visible. If this secondary checkbox is enabled, then the numbering of the (sub)titles will remain numbered.
The hide numbering settings are “inherited” by descendant clauses, and can even be changed on a descendant level. For example, if the grandparent clause hides its numbering except for the titles, then those settings will be inherited by its child clauses, grandchild clauses, and so on. However, any of those descendants can change the setting — e.g., a grandchild clause can hide its own title numbering and the title numbering of its further descendants.
The only limitation is that once numbering gets completely hidden (i.e., including the title numbering), it is not possible to re-enable the numbering at some descendant level. The underlying reason that otherwise “gaps” in the numbering could become visible — e.g., a grandparent clause 1. that is itself not numbered, would have an unnumbered child clause, and a grandchild clause 1.1.1 that is numbered.
Force headings (numbers) into bullets
As its description implies, the checkbox converts numbered headings into bullets.
For example, if the body of a clause contains:
then enabling this setting will cause this clause’s instance to appear as if the following had been written instead:
This possibility is particularly useful to foster the reusability of a clause.
Show as left column of the next clause
The checkbox is intended as a shortcut for quickly creating two columns next to each other.
- In the MS Word output, you will notice that a single-row table with two 50% width cells will be created.
- Within ClauseBase, the two clauses will be shown next to each other with a red dotted line in between.
Start clause on a new page
When enabled, the checkbox will cause its clause instance to be the first paragraph on a page.
This setting is similar to what is achieved (for all clause instances) with the “page break before” setting in the custom styling > text flow settings of each paragraph part of the edit pane.
In the MS Word output, this is achieved by enabling MS Word’s “page break before” option in the detailed paragraph settings. Enabling this setting is strongly preferred over inserting multiple Enters (which will easily cause vertical shifting once the text size is changed, or paragraphs or clauses are inserted or deleted).
Enabling “page break before” in MS Word is often usually preferred over inserting a manual page-break (Ctrl-Enter, or through the Insert > Page break toolbar button), because this setting will be associated with the paragraph in question, so will always move together with the paragraph.
Here you can edit if and how the numbering and title of the selected clause is being shown, make sure the clause is being shown as the left column of the clause that follows, make sure a new page is started before the selected clause, add custom styling to the title and/or body parts of the selected clause etc.
As pointed out in the note above, any changes made in the layout section only apply to this specific instance of a (library) clause in the active document, and are not made to the library clause itself. This means that any future use of the library clause will not include the changes you make here. Please refer to this article for more information on where custom stylings apply.
If you want to change the custom styling of an adhoc clause, please use the edit pane.
In the layout subtab you can also make sure a clause is repeated. The drop-down list under “repeat clause” will show a list of all “list of texts”, “number” or “repeating list” types of datafields included in the document.
The clause will then be shown as many times as the number of items contained in the selected datafield. If, for example, the datafield “name” of the concept “party” is a repeating list that is selected under “repeat clause”, and three items were inserted into “name”, the clause will be shown three times.
Typical use cases for this functionality are party description clauses and signature blocks which can be repeated for as many times as there are parties (i.e. items entered into a repeating list datafield under the concept of your choice).
Don’t translate in multi-language output
This checkbox is only relevant when a document is exported in multiple languages at once. It allows you to specify that a certain clause should not be translated in such case, and should instead span across the different columns of the page.
This is typically only relevant for signature boxes in multi-language documents that actually get signed by the parties. Obviously, in such a scenario, the signature boxes should not be translated.
Tip: you may want to use the @in-language and @multi-language special functions to insert conditions and translate certain concept-labels or datafields in such uni-language paragraph.
This works similar to the document mapping function available under the document pane, except in this case the mapping is only applied to the selected clause. Two additional buttons are shown:
|show mappings that are ‘inherited’ from encompassing clauses||This toggles the visibility of mappings that are already applied either in the document itself or in the ‘parent’ clause of the selected clause (i.e. the clause of which the selected clause is a subclause).|
|‘map from’ selection only||By unchecking this, the ‘map from’ section will also contain concepts used in the document which are not used in the selected clause.|