Aside from document assembly through hand-crafted templates, you can provide your users with an auto-generated audit trail. In short, an audit trail is the list of actions the user takes. This means any questions answered, but can also include texts, tables and anything you want to add to it.
The easiest way to get started with audit trails is to ask our web team to turn it on as a (live) overview of answered questions in the same page as the question forms (if they haven’t already).
This widget will allow you, as the publisher, to place one to four useful tools at any point(s) in your model. Owing to the nature of the tools, it’s most likely you will wish to use them at the end of the model, hence the name.
This part of the audit trail tutorial explains how to fine-tune or tweak the contents of such an audit trail. Part 3 will teach you how to create your own design.
This section builds on the model and document of Introduction to Document assembly and further.
We highly recommend reading those articles first.
Furthermore, a basic understanding of conditions is advised.
Just as you can copy texts, images and so on in other software, you can copy and paste in the Berkeley Studio. Because there is a difference between how texts, nodes, graphs and actions are copied, we made different sections for them, except for texts.
To create the dataset briefly described in the introduction on datasets, first create a new model. In this model, add a node ‘add_dataset’ to our model. In this node, we will create our first dataset. To start, click [Actions > Dataset] to open the dataset window. The following screen will pop up:
When you have an empty grid in your model, upon which your end users
can add (or remove) rows, it can sometimes be useful to automatically
generate one or more rows. In this tutorial, you will learn how to
force just that.
We highly recommend reading the guided tour and understanding model flow before this section. Furthermore, some experience with the Berkeley Studio is recommended.
We often get the question whether it is possible to divide a model into different parts in order to increase the overview of the model. With the introduction of chapters we respond to this question.
The feedback widget allows users to directly send you feedback about a certain node in your model. For the widget to work, download the feedback model linked to at the top of this article and follow the instructions below.
To send an Email, select the menu item ACTIONS > Email. With Email, you can not only send Emails with optional attachments but also send Calendar Items. This enables you to make appointments with people, just as you would in Outlook or a similar program.
In the previousarticles, we learned how to create custom versions of basic input types. We set various constraints and properties, such as maximum text length and placeholder texts, and created reusable question types. These reusable input types promote consistency throughout your model(s).
In this part, you’re going to learn another trick that can be of great use in the making of models: repeats. We advise you to finish the guided tour first. It is also advisable to be familiar with model structure.
