| ... |
... |
@@ -54,56
+54,3 @@ |
| 54 |
54 |
: Aktiviert das Setzen eines Zielstatus für die gebildeten Vorgänge. |
| 55 |
55 |
; Zielstatus setzen |
| 56 |
56 |
: Hier sind alle definierten Status des Mandanten aufgelistet und, falls aktiviert, muss ein Status ausgewählt werden. |
| 57 |
|
- |
| 58 |
|
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 59 |
|
-~~~~~~~~~~~~~~~~~~~~ENGLISCH~~~~~~~~~~~~~~~~~~~~~~~~ |
| 60 |
|
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 61 |
|
- |
| 62 |
|
-This feature allows creation of form records and e.g. email invitation of persons to fill out this form. Data, including email adresses for the invitation, can be uploaded under data as a .csv file. |
| 63 |
|
-The datasource with all information that should be used can be selected in the invitation dialog. The number of invitations which can simultaniously be created depends on the license. |
| 64 |
|
- |
| 65 |
|
-== Process == |
| 66 |
|
- |
| 67 |
|
-After starting the process of inviting persons, a form record is produced for every row in the datasource. The form is prefilled if wanted (see configuration) and a target status for the created form can be set (see configuration). Each Email adress receives a link to the for itself created form, if email sending is activated (see conifguration). Based on this link, the receiver can edit or send the form record. |
| 68 |
|
- |
| 69 |
|
-== Configuration == |
| 70 |
|
- |
| 71 |
|
-An uploaded datasource in .csv format is required to use the invitation feature. It is recommended to use headers. The invitation can be configured via multiple required and optional settings. The dialog is divided into four parts: |
| 72 |
|
- |
| 73 |
|
-=== Datasource === |
| 74 |
|
- |
| 75 |
|
-; Datasource (.csv) |
| 76 |
|
-: All datasources of this mandant are listed here. The datasource which should be used can be selected here. |
| 77 |
|
-; From (row) |
| 78 |
|
-: The invitation process will begin from this row in the datasource. |
| 79 |
|
-; Number of entries |
| 80 |
|
-: This defines the number of entries which are used for the invitation process and consequently the number of form records that are created. The maximum number is dependent on the license. |
| 81 |
|
- |
| 82 |
|
-=== Email configuration === |
| 83 |
|
- |
| 84 |
|
-; Activation |
| 85 |
|
-: Activates the sending of emails to the content of the defined column of email adresses in the invitation process. |
| 86 |
|
-; Column of e-mail adresses |
| 87 |
|
-: All headers of each column in the datasource are displayed here. The column that contains email adresses should be selected here. The emails are sent to the content of this column. |
| 88 |
|
-; Email from |
| 89 |
|
-: Specifies the sender address of the invitation email. |
| 90 |
|
-; Sender name |
| 91 |
|
-: Specifies the name of the sender of the double opt-in email. |
| 92 |
|
-; Subject |
| 93 |
|
-: Specifies the subject of the invitation email. |
| 94 |
|
-; Message |
| 95 |
|
-: The text of invitation email. This should contain the (prefilled) form link. The form link is available via the [[variables>>doc:Formcycle.UserInterface.Variables.WebHome]] //[%$FORM_INVITE_LINK%]//. |
| 96 |
|
- |
| 97 |
|
-=== Prefill form === |
| 98 |
|
- |
| 99 |
|
-; Activation |
| 100 |
|
-: Activates prefilling of form elements during the invitation process. |
| 101 |
|
-; Datamapping table |
| 102 |
|
-: The form can optionally be prefilled with e.g. data from the datasource. If this option is active, a table with the mapping of form elements and columns of the datasource will appear. The first column of this table lists all form elements that can be filled. This column can be searched for specific form elements. In the second column, the content which will be prefilled can be specified. There are also placeholder which are dependent on the datasource which are replaced with the content of the specific column. These placeholders are available under über //[%$data.COLUMNNAME%]// for datasources with header or //[%$data.col1%]// for the first column of datasources without header. The third column of the datamapping table contains the button to edit that row and by clicking on the button of the last row, the mapping is deleted. If no value is specified in the second column, the form element will not be prefilled. |
| 103 |
|
- |
| 104 |
|
-=== Target status === |
| 105 |
|
- |
| 106 |
|
-; Activation |
| 107 |
|
-: Activates to set a specific status to a generated form record. |
| 108 |
|
-; Set target status |
| 109 |
|
-: All status that are defined for this form are listed here and one of them must be selected. |