I. Overview
1. Application scenarios
Filling can be saved temporarily means that the filling content can be archived. After the operation is interrupted, reopening the filling page can automatically read the file and continue filling.
As shown in the figure below, the filled data will remain after the page is refreshed.
2. Functional logic
Including two ways of manual staging and automatic staging.
Staging data is saved in the platform database. After the clear function is used or the submission is successful, the temporary data will be deleted.
Temporary data is saved according to the logged in user.
It does not support temporary images and files uploaded by the file control, mobile terminals, and templates with charts are not supported.
Does not support staging page data based on different query parameters
II. Temporary storage mode
1. Manual stash
Manual stash refers to adding a Stash button in the data entry toolbar. After clicking this button, the filled data will be archived.
Add button method: Designer menu bar, click Template > Web Attributes, open the editing interface, select Data Entry Settings > Individually set for the template, selectStash button, add to the top toolbar.
When data entry preview, the manual save operation is shown in the following figure:
2. Auto stash
Auto stash means that as long as the user fills in the data, the system will immediately archive the data.
Setting method: in the designer menu bar, clickTemplate > Web Attributes, open the editing interface, select Data Entry settings > Individually set for the template, and check Auto Temporary Storage.
When filling in preview, the effect of automatic temporary storage is shown in the following figure:
III. View temporary storage
The temporary data stored in the fineDB database PUBLIC.FINE_WRITE_STASH table.
1. New data connection
In the designer menu bar, click Server > Define Data Connection to create a new JDBC data connection, as shown in the following figure:
The connection configuration is shown in the following table:
| Attribute | Value |
|---|---|
| Database | others |
| Driver | com.fr.third.org.hsqldb.jdbcDriver |
| URL | jdbc:hsqldb:file://${ENV_HOME}/embed/finedb/db |
| User name | sa |
| Password | no password required |
Note: the URL in the table is common under Windows/Linux/Mac.
2. View temporary data
Create a new data query dataset, select fineDB as the database, and the sql statement is:
select * from PUBLIC.FINE_ WRITE_ STASH
PUBLIC.FINE_WRITE_STASH contains the temporary data, as shown in the figure below
The fields of the table are described as follows:
| Field | Description |
|---|---|
| ID | primary key |
| DATA | temporary data, save as CSV format, cell + content |
| REPORTPATH | report path, physical path, not platform path |
| USERNAME | User name |
IV. Empty temporary storage
Add a clear button in the toolbar. Click this button to manually clear the stored data.
Add button method: Designer menu bar, click Template > Web Attributes, open the editing interface, select Data Entry Settings > Individually set for the template, select Clear button, add to the top toolbar.
When data entry preview, the manual clearing operation is shown in the following figure:
V. Precautions
The data decision system does not open the template authentication, users do not log in to the system, they can directly access the filling template through the URL.
At this time, the temporary data, database tables PUBLIC.FINE_ WRITE_ The username field of static is empty. The data temporarily stored by different users can be shared and viewed with each other.
If you want to avoid the above problems, the decision system needs to turn on the template authentication, and force the user to view and operate the template after logging in. For the method of turning on the template authentication, see the document: template authentication
