Rerun phases
A rerun of a Document Pack Template is based on the Document Pack containing all versions of the Data Backbone from the initial run. It consists of two phases:
-
Rerun of the Data Preparation Template
-
Rerun of the Document Templates
At each step of the rerun, Data Backbones are merged. In this process, the main version of the Data Backbone overwrites the other one and only these parts of the other Data Backbone that are not present in the main version remain. The initial version of the Data Backbone takes the value from the output Data Backbone only if this value is missing in its own field.
Data Preparation Template rerun
The prepared Data Backbone produced earlier is now used to rerun the Data Preparation Template. During the first merge between the original input Data Backbone and the prepared Data Backbone, the input Data Backbone becomes the main. It results in a merged input Data Backbone. Then, the Data Preparation Template is run using this merged input Data Backbone.
The Data Preparation Template modifies the Data Backbone either directly or based on interaction with the user, which results in a new prepared Data Backbone.
Document Template rerun
For each Document Template, the new prepared Data Backbone is merged with the template result Data Backbone of the initial run. Now, the new prepared Data Backbone serves as the main data source and a slot-specific merged prepared Data Backbone is produced as a result.
During the merge process, each slot uses the prepared Data Backbone as input and subsequently does not require the template result Data Backbones.
Then, the Document Template is run using the merged prepared Data Backbone, which results in an output document and a new template result Data Backbone.