Datafield options

When you create a datafield, you immediately see a wide array of optional values you can designate for it.

Below, we discuss each button and its function.

Label

Labels act as alternative names that can be formulated in more understandable language than regular datafield names.

Since datafield names cannot use spaces between words and are generally quite brief, it may be confusing to users to know what is meant by them. Take for example the question if a commercial agent has or does not have an exclusive relationship with their principal. This question could be formulated in the following condition:

#agent^exclusive = true

or

#commercial-agency^exclusive-relationship-between-principal-and-agent = false

In both cases, it is not out of the question that subsequent users are confused when they see this short or lengthy version. Since labels are not subject to the requirements of brevity and no use of spaces, you are free to phrase the question this condition embodies in a much more understand way, for example: Does the agent have an exclusive relationship with the principal?

This label will be shown in the tab of the operations panel and will also be shown as the standard question in the Q&A when you insert it via mode in the menu.

Aliases

When you create a name for a datafield, you will do this in the language of your choice. However, it may be desirable to provide translations for this name if you are in the habit of uploading clauses in multiple languages. That is where aliases come in.

Aliases allow you to give additional names to datafields and tie them to a specific language. This allows you to refer to the same datafield with different names. When you, for example, use the English alias of a datafield in the Dutch version of a clause, you will be given the opportunity to automatically "translate" the English alias to the Dutch alias. In the example below, this can be done by clicking "to nl"

Predefines

Introduction

Predefines are, as the name suggests, predefined values for particular datafields. They are primarily used as aides for users who make use of clauses that contain datafields.

Say you have created a condition where, upon filling out the applicable law of the contract, the competent court is filled out as well. This condition could look like this:

Any disputes arising out of #°contract shall be submitted the courts of {#applicable-law^country= "France": Paris | = "Belgium": Brussels | = "Netherlands": Amsterdam}.

Naturally, users must be aware that they have to fill out either "France", "Belgium" or "Netherlands". To help them use this datafield, you can set these values as predefines. When users are about to assign a value to this datafield in assemble document, they will have the option to select from these predefined values, thus ensuring they can make optimal use of the intelligence embedded in the clause:

When you insert this datafield into a question via the option in mode, the predefines will also automatically be displayed.

Fixing the predefined values

In the example condition above, no account is taken of the situation where the applicable law is not French, nor Belgian or Dutch. Therefore, the condition would not work when, for example, "Germany" is filled in as a country. To avoid that situation, you can check the following option when editing the predefines:

This will prevent users from filling out a value that is not included in the predefines list and thus ensure that datafields that make extensive use of certain values function correctly.

Optional labels

Much like datafields themselves, predefines can also use labels. This can be useful for the situation where you use an abbreviated version of the value for the sake of brevity (e.g.: "prop-dmg" instead of "property damage"). To activate these labels, simply click when filling out the predefines.

Special tags

ClauseBase integrates with virtually every company register in the world. You can designate special tags from a predefined list to link your datafields with certain party-specific variable fields. This way, users who use questionnaires to generate contracts can quickly draw information from those registers by simply searching for a company's name or company number.

For example, say you have the concept "Purchaser". The Purchaser is a party to a contract meaning their name, address and company number (at the very least) should be present in the agreement. For these three distinct datafields, you can add the following special tags:

  • Name: entity-name
  • Address: any of the following special tags - entity-street, entity-street-nr, entity-street-nr-zip-city, entity-zip, entity-city
  • Company number: entity-number


How did we do?


Powered by HelpDocs