
Under the datafields pane (also called the data dashboard), you get an overview of all datafields used in the active document, grouped by default by:
- the concepts to which the datafields are connected; and
- the categories to which the different concepts belong.
Each datafield that does not have a value assigned yet, will have an icon showing the type of the datafield and may be assigned a color by the creator of the datafield (dark grey is the default color).
- At the left of each datafield, you will also see a magnifying glass icon
. When you click on it, you will see a popup-list that provides an exhaustive list of all the clauses where the datafield is used.
- When you click on a datafield that does not yet have a value, a default value will be assigned to it. You can then modify the value anyway you like.
- When some value is assigned to a datafield, you can click on the label of the datafield to scroll to and highlight the first clause where this value is currently used in the document/binder.
Options
Popup-menu
When clicking on this icon, you will be shown a popup-menu that enables you to toggle the following options:
- toggle grouping of datafields by category
- toggle showing of datafields without a value assigned
- clear all datafields
- save the values currently assigned to the datafields as a standard set
- select one of the saved sets of datafield values (cf. previous bullet)
Show unused 
When this option is enabled, ClauseBase will include all datafields that are mentioned somewhere in a clause. When this options is disabled (the default), ClauseBase will only include datafields that are actually currently used.
alpha {#contract^value > 5000: #contract^name} beta
, and datafield #contract^value
is currently set to 2000, then #contract^name
will not be visible. If no other clause would currently use datafield #contract^name
, then this datafield will be omitted from the data dashboard — except if show unused is visible. Similarly, in a condition such as
#contract^value > 5000 and #applicable-law^name = "Dutch"
, datafield #applicable-law^name
will not be “used” when the contract’s value is currently set to 2000, because ClauseBase will immediately stop evaluating the condition at the moment it notices that #contract^value
is lower than 5000, as there is no need to perform any further evaluation.Clause enablers 
Toggling this option will show/hide datafields that act as clause enablers, i.e. datafields used in the “enabled?” condition of a clause.
#contract^value > 5000 and #applicable-law^name = "Dutch"
, both #contract^value
and #applicable-law^name
will qualify as clause enablers.Text enablers 
Toggling this option will show/hide datafields that act as text enablers, i.e. datafields used within conditions that are used in the title or body text of clauses to show/hide parts of a clause.
Alpha {#contract^value > 5000: beta}
, datafield #contract^value
will qualify as a text enabler, because it enables/disables the visibility of text part “beta”.Others 
Toggling this option will show/hide datafields that do not act as clause or text enablers.
For example, if the body of a clause contains the following text: Alpha #contract^value beta
, then #contract^value
will qualify as “other” datafield.
Bulk 
This button — only visible for advanced users — brings you to a mode to make multiple exports of the active document in one action. An Excel sheet containing all datafields will be generated which can be re-uploaded after which the documents (pdf or docx) will be exported.