Types of changes
This change will remove a specific clause (and all its descendant clauses) from the document or binder.
In order to select the relevant clause, you will have to select the clause in a document or binder pane and click on the "use selected clause in document pane" button. You will then see a preview of the selected clause in the green box that appears.
If you want to select another clause instead, then click on the trash icon at the right side, and then select another clause.
If a certain clause happens to be repeated at different places of a document or binder, then you can optionally specify that all these instances of the clause need to be deleted. If this option is not activated, then ClauseBase will locate a clause by looking at the clause ancestors and the position of the selected clause to its closest ancestor.
At the moment that ClauseBase needs to apply this change, it may happen that the salary clause is actually no longer the fifth clause in the document, for example because some other clause before it was also deleted. ClauseBase will then use the first clause it can find at the same level.
Obviously, these difficulties in finding the correct clause are irrelevant when the "disable clause everywhere" option has been selected, because ClauseBase can then simply find all instances of the same clause, and delete them everywhere.
As its name implies, this change will replace a specific clause with another clause.
In order to use this clause, you will have to select a certain target clause in a document / binder pane, and then click on the "use selected clause in document-pane" button. In addition, you will have to select an alternative clause from the clause library by clicking on the "select clause..." button.
If you want to choose another target clause or replacement clause, you can click on the relevant trash can at the right side.
This change allows you to insert a clause at a specific location within the document or binder.
- In the document / binder preview pane, you need to select the clause that will act as the ancestor clause, i.e. below which the new clause will be inserted.
- You can choose the clause to insert by clicking on the "select clause..." button. A dialog box will then appear that allows you to navigate to the relevant clause in the file system.
- With the dropdown list, you can choose whether to insert the clause as the first or last descendant of the ancestor clause, i.e. the first or last subclause.
The primary means to change a datafield, is to directly bind it to a specific question by modifying the options of that question.
However, there exist situations where this is not enough — for example when:
- the same answer to a question needs to be inserted into multiple datafields
- an answer should only be inserted into a datafield when a certain condition is met
- under certain conditions, a specific value (not submitted by the user) should be inserted into the datafield
All such situations call for a "change datafield".
To use this type of change, you obviously need to select the datafield that you want to select.
Next, you will have to choose whether to insert a specific value (i.e., a value that is not submitted by the user), or a value obtained from a user's answer to some question.
A bulk change allows you to update several datafields at once. To use this functionality, several items need to be simultaneously prepared. Please refer to the separate page on bulk changes for more information.
This type of change is very similar to directly changing a concept-label in Assemble Document.
After having selected which term to change, you essentially have to choose where the new term will come from:
- either a specific value decided by you, by filling in the singular and/or plural boxes at the left side;
- or an answer submitted by your user, by choosing the relevant question in the dropdown list(s) at the right side
Note that the default number (singular or plural), the gender and the article cannot currently emanate from the answer to a question. If you have to provide different possibilities here, you will have to create separate change sets that are subject to different conditions, and populate those change-sets with different settings for change term.