2018.2

Note that with multiple clones, the next clone is always added after the previous clone.
With addBefore(), the code original.addBeforeclone1); original.addBefore(clone2); will
result in "clone1, clone2, original".
With addAfter() the code original.addBeforeclone1); original.addBefore(clone2);"
results in "original, clone1, clone2".
Note
Calling clone() multiple times before calling addAfter() or addBefore() currently
won't work, as each next clone will get the same default name and replaces the previous clone. To
avoid this you should either explicitly assign a unique name to each clone (i.e. not rely on the
default name), or call addAfter() or addBefore() before calling clone() again.
Renaming a clone
By default, clones receive the name of their source section with a "Clone {sequence}" suffix, for
example:
Source: "Section 1"
Clone Name: "Section 1 Clone 1"
Use the name property to assign the cloned section another name, for example:
clone.name = "my_section_clone";
To ensure that CSSrules and scripts can target a specific clone, that clone's name should be
unique (within the scope of a single record, that is; across records, the same name can be
used).
Targeting elements in a cloned section
Clones that have a unique name can be further personalized with the use of CSS style sheets
(see "Styling and formatting" on page645) and personalization scripts (see "Variable Data" on
page702 and "Writing your own scripts" on page722).
The selector to use is: [section="name of the clone"].
The following CSS style rules target the <h1> element in a number of clones and assign the
respective text a different color:
Page 762