Hide last authors
gru 42.5 1 {{figure image="form_inbox_en.png"}}
nlo 29.1 2 {{id name="fig_form_inbox_dialog" /}}
gru 42.5 3 Inbox dialog of a form.
nlo 29.1 4 {{/figure}}
5
nlo 42.1 6 {{content/}}
7
gru 42.5 8 The inbox dialog of a form can be opened via the //Inbox// button {{ficon name="inbox"/}} of the [[form menu>>doc:Formcycle.UserInterface.MyForms.WebHome||anchor="form_menu"]].
nlo 31.1 9
gru 42.5 10 == General settings ==
nlo 10.1 11
gru 42.5 12 * {{litem title="Subject"}}The subject of a form allows for naming of incoming [[form records>>doc:Terminology.WebHome||anchor="form_record"]]. [[Placeholders>>doc:Formcycle.UserInterface.Variables.WebHome]] can be used for the form subject. By Default the subject consist of the form title and the form record ID (//[%$PROJECT_TITLE%] - [%$RECORD_ID%]//).{{/litem}}
nlo 13.1 13
gru 42.5 14 * {{litem title="Default inbox"}}All forms that have been submitted are put as form records in the inbox. If this setting has not been changed, all form records will be put into the system inbox //Default inbox//. This option allows you to change the inbox.{{/litem}}
nlo 9.1 15
gru 42.5 16 * {{litem title="Allow state transitions in inbox"}}Whether users are allowed to perform state [[state>>doc:Formcycle.UserInterface.MyForms.WorkflowProcessing.States.WebHome]] changes for form records of this form in the [[inbox>>doc:Formcycle.UserInterface.MyForms.Inbox]].{{/litem}}
nlo 9.1 17
gru 42.5 18 The standard inbox contains form records of different forms always shows certain fixed columns, ie. project ID, form record ID, process ID, date of submission, date of most recent change, and state. Form records may also be viewed in their own form-specific inbox with customizable columns.
nlo 36.1 19
gru 42.5 20 == Configuring form specific inboxes ==
21
22 {{figure image="inbox_project_view_en.png"}}
23 Project specific view selected in the [[inbox>>doc:Formcycle.Inbox.WebHome]].
awa 38.2 24 {{/figure}}
nlo 32.1 25
gru 42.5 26 {{figure image="pr_postfach_normal_en.png"}}
27 Standard inbox.
awa 38.2 28 {{/figure}}
29
gru 42.5 30 {{figure image="pr_postfach_projekt_en.png" width="300"}}
31 For form specific inboxes, the system stores a separate table with the inbox configuration.
awa 38.2 32 {{/figure}}
33
gru 42.5 34 The defualt view of the [[inbox>>doc:Formcycle.Inbox.WebHome]] shows all [[form records>>doc:Terminology.WebHome||anchor="form_record"]] the user has access to. This depends on the [[State>>doc:Formcycle.UserInterface.MyForms.WorkflowProcessing.States.WebHome]] of the [[form record>>doc:Terminology.WebHome||anchor="form_record"]], the [[groups>>doc:Formcycle.UserInterface.UserSettings.UserGroups.WebHome]] the user is in and the set filters of the inbox.
awa 38.2 35
gru 42.5 36 Alternatively a "Form-specific data view in the mailbox" for the form can be defined by configuring the columns that should be displayed.
nlo 22.1 37
gru 42.5 38 The list at the bottom of the inbox dialog shows the configuration of the form inbox view. The list on the right hand side shows all form fields available for the current version of the form. The list on the left hand side shows all columns that will be shown in the custom inbox for this form. Use the buttons between the two lists to move form fields between the two lists.
nlo 22.1 39
gru 42.5 40 As soon as a user in the inbox gains access to tasks of this form, an additional option to display the view configured here will appear.
gru 38.3 41
gru 42.5 42 {{version major="6" minor="4" patch="0"/}} Starting with {{formcycle/}} version 6.4.0 technical elemente like //ID//, //Subject// and //Inbox// can be shown or hidden as required. To differentiate between normal form elements, which have {{ficon name="inbox"/}} symbols in front of their names in this dialog, technical elements are marked by a {{ficon name="settings2"/}} symbol.
gru 42.2 43
gru 42.5 44 === Database tables ===
nlo 36.1 45
gru 42.5 46 After a form has been submitted, all submitted data will be stored in a database table of the system. For the standard inbox, the system will generate the view with the columns available, which may depend on the user's permissions, the form's state and the inbox.
nlo 7.1 47
gru 42.5 48 For the form specific inbox, the system dynamically creates one more database tables for each form. It contains the custom columns as configured for each form.
gru 1.1 49
gru 42.5 50 === Column alias ===
gru 1.1 51
awa 38.2 52 {{info}}
gru 42.5 53 Please note that the column alias is different from the form field alias. Initially, when you create a new inbox configuration, the column alias is set to the form field alias. When you later change the form field alias, the column alias is not updated automatically.
awa 38.2 54 {{/info}}
55
gru 42.5 56 An alias can be set for form field in the list on the left hand side by clicking on the edit icon. When an alias has been set, it will be used as the column name of instead of the form field's name.
gru 1.1 57
gru 42.5 58 === Reinitialise inbox ===
gru 1.1 59
gru 42.5 60 Have changes been made to the inbox view configuration, clicking the //Save// {{icon name="save"/}} or //Reinitialize// {{icon name="refresh"/}} button will (re-)intialize the form inbox table.
61 This will read the current inbox settings and recreate the dynamically created database table. This makes it possible to change view of the custom inbox at any time. Depending on the number of form records this may take several minutes.
Copyright 2000-2024