LogoLogo
ClausesDatafieldsSpecial FunctionsStylingQ&AAPI
  • Welcome!
  • Getting started
    • What is Clause9?
    • Structuring your clause library
    • Structuring your clauses
    • Drafting modes in Clause9
    • Creating a questionnaire
    • Sample clauses
    • Videos
      • Concepts and datafields
      • Conditions
      • Q&As
      • Binders
      • Styling
      • Enumerations
      • Tables
      • Definitions
      • Snippets
      • Cross-references
      • Special functions
      • Examples of common clauses
      • Import clauses from MS Word
      • Grammatical conjugations
      • Action buttons
      • Alternative clauses
  • Assemble document
    • Document toolbar
    • Clause hierarchies
    • Focus Mode
    • Bulk generation of documents
    • Exporting documents
    • Assemble Document - FAQ
    • How to: Assemble Document
      • Insert images
  • Assemble Document Operations Panel
    • Operations panel
    • File pane
    • Edit pane
    • Document pane
    • Binder pane in the operations panel
    • Search pane
    • Browse pane
    • Terms pane
    • Data dashboard
    • Advanced pane
    • Styling pane
    • Miscellaneous pane
    • Visibility settings & actions menu
  • Binders
    • Binders: general
    • Styling cross-references to subdocuments
    • Global and local definition lists
    • Document and binder properties
    • Styling of a Binder versus subdocuments
    • (Un)locking documents in a binder
    • Binders - FAQ
    • How to: binders
      • Make a subdocument in a binder conditional
  • Clauses
    • Introduction to clauses
    • Clause structure
    • Grammar sheet
    • Writing conditions
    • Examples of conditions
    • Using codes instead of text fragments
    • Bold, italic and underline
    • Special codes
    • Enabled?
    • Links
    • Cross-references
    • Introduction to tables
    • Deviating table styling
    • Shrinking clauses
    • Action buttons
    • Enumerations
    • File position
    • Snippets
    • Parameters
    • Conjugations
    • Mixing data types
    • For-loops
    • Clause versioning
    • Abstract article references
    • Advanced multi-language features
    • Clauses - FAQ
    • How to: clauses
      • Create an ad-hoc clause
      • Create a library clause
      • Make a clause repeat
      • Make a paragraph within a clause conditional
      • Use a shortcut to refer to a concept
      • Insert a line break or page break
      • Creating a list with both predefined options and free input
      • Defining alternative clauses
      • Creating cross-references
      • Creating signature blocks
      • Creating advanced party introduction clauses
      • Automatically numbered annexes or schedules
      • Reuse any clause in a different context
      • Setting MS Word document properties
      • Add action buttons to clauses
      • Electronically signing documents
  • concepts
    • Introduction to concepts
    • Creating concepts
    • Concept labels
    • Links
    • Organising concepts
    • Concepts - FAQ
    • How to: concepts
      • Add predefines to a datafield
  • Datafields
    • Introduction to datafields
    • Types of datafields
    • Rules of thumb for using datafields
    • Data-expressions
    • Datafield aliases
    • Datafield labels
    • Datafield special tags
    • Datafield descriptions
    • Repeating list datafields
    • Datafield predefines
    • Datafields - FAQ
    • How to: datafields
      • Change datafield type
      • Change the datafield's name or alias
  • Definitions
    • Introduction to definitions
    • How to: definitions
      • How do definitions work?
      • Create a definition
  • Files
    • How files are organised
    • Browse files
    • File types
    • Custom styling
    • Legal comments
    • File description
    • Attributes
    • Reporting
    • File name
    • File category
    • Access rights
    • How to: files
      • Creating advanced folders
      • Naming your files
      • Shortcuts to folders or files
  • Q&A
    • About cards
    • Cards pane
    • About changes
    • Changes pane
    • Types of changes
    • Adding conditions
    • Question options
    • Copying & pasting answers
    • Comments, notes & documentation
    • Interactive Q&A inspection
    • Embedding questions into a document
    • “Changes” button
    • Batch create pane
    • Identifiers pane
    • Import pane
    • Edit clauses pane
    • Q&A options
    • Q&A - FAQ
    • How to: Q&A
      • Create predefined answers to a question
      • Add disclaimers
      • Create categories of questions
      • Modify the exported filename
      • Create a question to change the language of a document
      • Send a questionnaire to someone without a ClauseBase account
      • Create questions for repeating list datafields
      • Selecting legal entities & addresses
      • Create a questionnaire using "batch create"
      • Launch other Q&As
    • Leveraging ClauseBuddy Smart Templates in Clause9
  • Import
    • Introduction to importing clauses
    • Uploading clauses
    • Defined terms in Import mode
    • Datafields in Import mode
    • Cross-references in Import mode
    • Assigning folders
    • Conversion process
    • Exporting
    • Stashing intermediate results
    • Tips, tricks & limitations
  • Styling
    • Styling overview
    • Base styling
    • Numbering
    • Definitions styling
    • Enumerations styling
    • Locale styling
    • References styling
    • Page styling
    • Styling of a Binder versus subdocuments
    • Styling: tips and tricks
    • Advanced styling topics
    • Copying headers and footers from an MS Word file
    • How to: styling
      • Using custom fonts
      • Change bullet styling
  • Special functions
    • Introduction
    • Calculations
    • Concepts
    • Conditions
    • Conjugations
    • Content Control Elements
    • Datafields
    • Dates & durations
    • Languages
    • Lists
    • Numbers
    • References
    • Repeating (looping)
    • Special items
    • Text structure
    • Text modification
    • User
    • Q&A
  • Settings
    • Account
    • Preferences
    • Access bundles
    • Favourites
    • Saved searches
    • Saved datafields
    • Styles
    • Default styles
  • Admin
    • General
    • Users
    • User rights
    • Profiles
    • Groups
    • Styles
    • Default styles
    • Attribute models
    • Usage page
    • Custom homepage
    • Global placeholders
    • Access rights
    • How to: admin
      • Adding a new user
      • Disabling a user
      • Managing group memberships
  • Miscellaneous
    • Advanced tips & tricks
    • Typing special symbols on your keyboard
    • Shortcuts
    • Grammar style guide
    • Inserting MS Word files
    • Globo-panel
    • Creating high-quality documents
    • Excel calculations and lookups
  • Integrations
    • Overview
    • Spreadbases
    • E-signing documents
    • Drag & drop integrations
  • For developers
    • Clause9 API
    • Custom functions
    • Example custom functions
Powered by GitBook
On this page
  • Why use enumerations?
  • Grammar
  • Enumeration type
  • Skipping the final suffix
  • Enforcing bullets
  • Item separators
  • Optional item number
  • Using conditionals
  • Using special functions
  • Forcing * bullets into an enumerated list
Export as PDF
  1. Clauses

Enumerations

PreviousAction buttonsNextFile position

Last updated 2 months ago

Enumerations (French: énumération / Dutch: opsomming / German: Aufzähung) are used to create lists of items. Depending on the applicable styling settings for enumerations and the content of each item, those items will then be formatted either as an “inline” list of items, or as a bullet-list, as shown in the next example:

Why use enumerations?

You may wonder why you would want to use the special enumeration code, instead of manually typing in the items. The benefits of using the special codes include:

  • The formatting will be automatically determined, through a combination of the length of each item and the applicable styling settings for enumerations. Without having to change legal content, you will be able to accommodate both users who want a traditional list of romanette items — (i) … (ii) … (iii) … — and users who want a more modern, bullet-style list.

  • You will never have to worry again about numbering: Clause9 will automatically ensure that the right numbers are inserted, sequentially, without any gaps or duplicates. If a certain item is subjected to a condition that happens not to be fulfilled, then that item will not be shown, and all numbers following it will be adapted accordingly.

  • Suffixes are automatically inserted: depending on the chosen styling settings for enumerations and the type of list, a semicolon, full stop (.), &, “and”, “or”, or “and/or” will be inserted.

Grammar

The basic structure of an enumeration is as follows:

{ AND | item1 | item2 | item3 }

Enumeration type

Right after the opening accolade you have to choose the type of enumeration — AND, OR, AND/OR or LIST. This will respectively result in a list that uses suffix “and”, suffix “or”, suffix “and/or”, or no suffix at all after the item(s).

Whether this suffix is actually repeated after each item, or instead only after the penultimate item, depends on the enumeration styling settings.

Skipping the final suffix

You can also choose AND-SKIPFINAL, OR-SKIPFINAL, AND/OR-SKIPFINAL or LIST-SKIPFINAL as the enumeration type. If the enumeration happens to get outputted as a bullet-list, then the final item will not get a suffix. The example above (if it would happen to get printed as a bullet-list) would then look as follows:

Enforcing bullets

In principle, whether an enumeration is printed inline or as bullets, depends on the applicable styling settings for enumerations. However, you can force an enumeration to always be printed as bullets — so irrespective of the layout-settings — by adding an exclamation-mark after the list type. For example:

{ AND! | item1 | item2 | item3 }

{ AND-SKIPFINAL! | item1 | item2 | item3 }

Item separators

Each item should be separated by the pipe symbol ( | ).

Optional item number

Right after the pipe symbol, you can optionally insert a number. If the enumeration then happens to get printed as an inline list, each item of the enumeration will be preceded by a sequential number. For example:

{ OR | 1. alpha | 2. beta | 3. gamma }

as an inline list, this will result in the following output (assuming that romanettes are chosen in the styling settings for enumerations):

(i) alpha, (ii) beta; and (iii) gamma

Including the optional number will have no effect if the enumeration gets printed as a bullet-list.

The actual numbers that are typed in, do not matter much — whether you nicely type in 1., 2. and 3., or instead a non-sensical sequence such as 45., 9. and 333., does not matter. In the future, Clause9 may use the actual number to allow you to cross-reference other items, but such functionality is not yet enabled.

Using conditionals

If you subject the content of an item to a condition, then the item may get skipped, depending on whether the condition is fulfilled. Clause9 will automatically ensure that the right numbering is used. For example:

{AND | 1. {#employee^gender = "male": alpha } | 2. beta | 3. gamma }

If #employee^gender happens to be false, then the enumeration would be shown as follows (assuming that the styling settings allow for an inline list):

(i) alpha; (ii) beta; and (iii) beta

If, instead, #employee^gender happens to be true, then the enumeration would get printed as follows:

(i) beta; and (ii) beta

Using special functions

Enumerations can also be created using one of the following special function calls:

Both special functions have some variations (see @bullets-and, @enumerate-numbered, etc.)— see the detailed explanations for both functions.

(i) key card; (ii) confidential documents; (iii) car; and (iv) car keys.

Forcing * bullets into an enumerated list

If your clause should contain actual bullets (i.e. with asterisks), you can still force the bullets into an enumerated list by inserting * AND or * OR as the very first bullet. For example:

1. This list will be shown with an "and" before the final item:

* AND

* apple

* banana

* cucumber

— taking as a parameter a list. Whether the enumeration is printed inline or as bullets, depends on the styling settings and the contents of the items.

— like @enumerations, but always prints the enumeration as a bulleted list, similar to using an exclamation mark after the list type

Using these special functions is most useful when the items you want to print, happen to be stored in a datafield. For example, if #employee^items-to-return is a datafield that contains a list of items to be returned, then would print such list as follows (assuming that inline printing applies per the styling settings):

@enumerate
@bullets
@enumerate-numbered-and