... |
... |
@@ -1,6 +1,6 @@ |
1 |
1 |
{{figure image="export_persistence_en.png"}} |
2 |
2 |
User interface for actions of type //Export to persistence file//. |
3 |
|
-{{figure}} |
|
3 |
+{{/figure}} |
4 |
4 |
|
5 |
5 |
Action of type //Export to persistence file// allows to provide the data of an operation as a persisted structure. This can be reloaded later to restore the form. This action and javascript code for loading the persisted values can thus be used to implement saving form data. |
6 |
6 |
|
... |
... |
@@ -39,7 +39,7 @@ |
39 |
39 |
|
40 |
40 |
== Import form data from export file == |
41 |
41 |
|
42 |
|
-If a form is called and there is a non-empty upload field named {{code language="none"}}fcp_persistence{/code}} in the form or there is a file named {{code language="none"}}fcp-persistence{/code}} in another upload field, the values from the persistence file will be written to form when the form is delivered, thus pre-populating fields. |
|
42 |
+If a form is called and there is a non-empty upload field named {{code language="none"}}fcp_persistence{{/code}} in the form or there is a file named {{code language="none"}}fcp-persistence{{/code}} in another upload field, the values from the persistence file will be written to form when the form is delivered, thus pre-populating fields. |
43 |
43 |
|
44 |
44 |
The following example code allows to realize this process with a button. Here, the form's target is set to its own URL on submit and all input fields except the upload field are disabled. Then a submit of the form is executed, through which the contents of the file are loaded. |
45 |
45 |
|