...
The ConfiForms Plugin app uses Confluence's page permissions to control form use. Users with 'edit' permission for a page have administrative rights for the form(s) defined on that page. By restricting 'edit' rights to the page, the administrator controls administrative rights to its form(s). See more on Confluence page permissions and ConfiForms
Each record stored with ConfiForms has an owner. This means that a user who owns the record can fully control it (if edit/delete is enabled by the administrator). Admin users of a form can configure ConfiForms records to be owned by themselves, and also by other users. A form's administrative users can control all records saved by the form.
A form can define additional users as form administrators or form superusers (even if they don't have edit permissions on the page).
Each record in ConfiForms has the following associated metadata (aka metadata fields):
Panel |
---|
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
Info |
---|
ownedBy and createdBy are now User objects and you can access all user object properties! See here: Accessing field values and properties |
Info | ||||||
---|---|---|---|---|---|---|
Looking for
But please look at the Differences between ConfiForms server/data center and ConfiForms cloud for more details on compatibility between cloud and server/dc versions of ConfiForms |
All these metadata fields, in addition to the form's defined fields (definitions), can be referenced using the "ConfiForms Field macro" in these ConfiForms macros:
Also there is a "IFMatches" macro which can be used inside CalendarView and ListView to enable showing/hiding blocks of content based on the ConfiForms field values
Info |
---|
Take a look at this page which demonstrates how the data can be shown: Multiple ways to show your form data in Confluence with ConfiForms |
ConfiForms (FormView) Registrations Control | ||||||
---|---|---|---|---|---|---|
| ||||||
Take a look also at conceptual view over all macros from ConfiForms app - ConfiForms app detailed view over the plugin macros
Excerpt Include | ||||
---|---|---|---|---|
|
ConfiForms Form (Definition)confiform | The main macro to define the entry form and its rules
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ConfiForms Field Definitionconfiform-field-definition | The macro to use inside the ConfiForms Form macro to define the form's fields, their types, and behaviour.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ConfiForms Registration Controlconfiform-entry-register | This macro defines how the form is displayed (as a pop-up dialog or embedded in the page) and the form's behaviour when submitted. Multiple 'Registration Controls' that use the same form (form definition) can be placed on one or multiple pages. When the macro has a body defined, the fields in the body will be used as inputs for the form layout. To enable WYSIWYG mode, make sure that "ConfiForm Field" macros are in the body of the "ConfiForms Registration Control" macro. ConfiForm Field macros and text can be styled as needed. If the "ConfiForms Registration Control" macro is not defined (empty), a default layout will be used (either as a table or a card with key-value fields).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ConfiForms Edit Controlsconfiform-entry-edit | This macro defines the behaviour of the Edit control for ConfiForms ListView and TableView.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ConfiForms TableViewconfiform-table | The macro to display stored data as a table, with instant search, filtering, and data sorting/ordering.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ConfiForms ListViewconfiform-list | This macro displays your stored data in WYSIWYG view (it also supports filtering and data sorting/ordering).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ConfiForms CleanViewconfiform-clean | This macro is very similar to ConfiForms ListView, but renders a more lightweight and cleaner output, allowing you to have better control over the rendered output (it also supports filtering and data sorting/ordering).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ConfiForms PlainViewconfiform-plain | This macro displays your stored data in plain view (it also supports filtering and data sorting/ordering).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ConfiForms CardViewconfiform-card | This macro displays your stored data as a vertical table (or card) with instant search, filtering, and data sorting/ordering.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ConfiForms CalendarViewconfiform-calendar | This macro displays your stored data in a calendar view.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ConfiForms ValueViewconfiform-value | This macro displays your stored data in a simple field view
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ConfiForms Form Fieldconfiform-field | This macro defines a field to be displayed within the ConfiForms TableView, ListView, or CardView macros
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ConfiForms IFTTT Integration Rulesconfiform-ifttt | This macro defines the integration rules for ConfiForms forms and is to be placed inside ConfiForms Form macro body. The macro body is used as the message body, task content, javascript snippet, page content, or request content, depending on the action type selected. The macro body completely supports referencing records, including the record owner as [owner], the record modifier as [modifier], and any record field as [entry.FIELD_NAME]. The body can include complex types; see "Subject for email / title for page / url for request" below for details. You can also reference existing Confluence templates to be used when IFTTT is used to create Confluence pages. To reference a template you will nee to add the following:
The template is looked up by the name, and first in Confluence space templates and then in global templates. If found the content is added to IFTTT macro body and used as a page template
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ConfiForms TableView Mergerconfiform-table-merger | This ConfiForms helper macro merges TableView results. This macro takes RICH TEXT as an input to define which fields (ConfiForms Field macros) to display and which tables to merge (in the ConfiForms TableView macros). It supports expressions which can be used when aggregating the data. Learn more in TableView Merger examples.
|
All these metadata fields, in addition to the form's defined fields (definitions), can be referenced using the "ConfiForms Field macro" in these ConfiForms macros:
confiform
The main macro to define the entry form and its rules
ConfiForms Form name | formName | The name of the form being created. This name be unique within the page and use alphanumeric characters [a-z, 0-9]. |
---|---|---|
Registration form title | registrationFormTitle | The title for the form to be displayed in the registration dialog. |
Save button label | saveButtonLabel | The text for the 'Save' button in the registration dialog. |
Enable full audit | enableAudit | If set, this enables a full audit, tracking all the changes made to the form and enabling a change history for versioning purposes. The form's admin users are able to see the log as a part of the admin user interface. |
Secure storage | secureStorage | When set, if a form has fields of type file then additional subpages with restricted access will be created to hold those files (as page attachments) and enable secure access. Form admins and a record original creator will have access to these attachments for download |
Lock form | locked | Use this flag when the ConfiForm should be locked so that additional records cannot be stored. Admin users will still be able to manage the form's data. |
Lock message | lockedMessage | The message text that will be displayed to users when the form is locked. |
Enforce one entry per user | uniqueByUser | ConfiForms will ensure that only one record per user (ownedBy) is saved. |
Restrict record view for non-admin users | showOnlyOwnRecords | This parameter limits access for non-admin users so that only records owned by the user will be visible to this user. Admin users will still have access to all records. |
Read-only after submission | readonlyAfterRegistration | This sets the form to be read-only once the user has submitted it. Users who have not yet submitted the form will still be able to do so. |
Read-only message | readonlyAfterRegistrationMessage | When the 'Read-only after submission' parameter is set and the user has submitted the form, this text will be displayed. |
Track maximum capacity | maxCapacity | The maximum number of records that ConfiForms will allow to be submitted. |
Maximum capacity message | maxCapacityMessage | When the 'Track maximum capacity' flag is set and the maximum has been reached, this text will be displayed. |
Allow data export | export | Use this parameter to enable data export for non-admin users. The "Enable export" parameter on the TableView macro must also be set. |
Enable ''Print'' button | printEnabled | This parameter will enable a print button on the form. |
Display editable fields in Print view | printEditable | When this parameter is set, the form's fields will be displayed as editable entries in the Print view. When not set, the fields will be shown as read-only labels. When checked |
Additional form admin user names (or groups) | additionalFormAdmins | A comma-separated list of user names / user groups that should be treated as the form's administrators. This parameter can be used to lock the form's configuration but enable full control over the form's data to certain users. |
confiform-field-definition
The macro to use inside the ConfiForms Form macro to define the form's fields, their types, and behavior.
type
The field's type which defines how data can be entered in the field (datepickers for dates, dropdowns, etc.) according to these definitions:
This type provides for a group of radio buttons, which allow the user to choose a single exclusive option. This type can be especially useful with surveys.
4.3+
5.1+5.1+This field type permits easy grouping and presentation for entered data. Each status level is color-coded to foreground data groupings.
Important
Filtering by the status field can be a bit complex because each color has a constant value which is stored with the data according to this pattern:
Color | Constant | ||||||
---|---|---|---|---|---|---|---|
| default | ||||||
| error | ||||||
| current | ||||||
| success | ||||||
| complete | ||||||
| moved |
* The Compatibility column shows the Confluence version number with which this field type is compatible.
confiform-entry-register
This macro defines how the form is displayed (as a pop-up dialog or embedded in the page) and the form's behavior when submitted. Multiple 'Registration Controls' that use the same form (form definition) can be placed on one or multiple pages.
When the macro has a body defined, the fields in the body will be used as inputs for the form layout. To enable WYSIWYG mode, make sure that "ConfiForm Field" macros are in the body of the "ConfiForms Registration Control" macro. ConfiForm Field macros and text can be styled as needed.
If the "ConfiForms Registration Control" macro is not defined (empty), a default layout will be used (either as a table or a card with key-value fields).
ConfiForms Form name | formName | The name of the ConfiForm to which this registration control should be linked. This parameter is required when the macro is used by itself (not inside the ConfiForms Form macro). The name parameter can be skipped when the macro is configured inside the ConfiForms Form macro, and if not defined, the form name is automatically assigned. |
---|---|---|
Location page name | pageTitle | The name of the page on which the form is defined if not the current one; leave this blank if the form is defined on the same page. |
Embedded or Dialog? | embedded | Check this option to have the form embedded on the page, uncheck to display the form as a pop-up dialog. |
Submission button label | registrationButtonLabel | The text to be displayed on the submit button. |
Post save message | registrationMessage | The text to be displayed after a record been created. |
Key-value request parameters | presetValues | This parameter provides a way to preset values for certain fields in the form. These are listed as key-value pairs, separated by & (as request parameters) where the ''key'' is a ConfiForms Field name and the ''value'' is the data to be preset for the field. |
Enable auto enroll | autoenroll | Use this parameter when the form has preset values (key-value pairs) and can be auto submitted. Because the form can have multiple registration controls, the auto enroll can be combined with predefined data to enable one-click submissions, for example, to capture yes/no feedback. |
Valid redirect URL | redirectUrl | An optional location to which the user will be redirected after a successful ''save'' operation. This parameter supports parameters and references to record fields: the record owner can be referenced as [owner], the record modifier as [modifier]; and any record field can be referenced as [entry.FIELD_NAME]. |
CSS styles | css | CSS rules to be applied to the Submit button when the form is displayed as a pop-up dialog (when the form is embedded in the page, this button is not shown). |
Visible only to groups/users | restrictions | This parameter accepts a comma-separated list of groups and users to which this field will be visible. Leave this parameter blank if there are no restrictions. |
Hide control when stored data matches this criteria | hideIfMatches | ALL ConfiForms entries stored by the form referenced will be concealed when the items in this parameter are matched in the entry. The control itself will be hidden when the condition/filter given is met, and this parameter uses the same syntax as in filters . |
confiform-entry-edit
This macro defines the behavior of the Edit control for ConfiForms ListView and TableView.
Inline edit or in dialog | inline | Defines how the record edit should be done: through a dialog or inline on the page. |
---|---|---|
Display Edit and Delete buttons | showBoth | This parameter can be configured to conceal the 'Delete' action for non-administrative users, or to display both Edit and Delete. To conceal both Edit and Delete, do not define the 'ConfiForms Edit Controls' macro. |
Label for Edit button | editButtonLabel | The text to display on the edit button. |
Label for Delete button | deleteButtonLabel | The text to display on the delete button, which is actually a link in the user interface. |
Post update message | updateMessage | The text to display after a record has been updated. |
Hide control when stored data matches this criteria | hideIfMatches | The current ConfiForms entry stored by the form referenced will be concealed when the items in this parameter are matched in the entry. The control itself will be hidden when the condition/filter given is met, and this parameter uses the same syntax as in filters . |
confiform-table
The macro to display stored data as a table, with instant search, filtering, and data sorting/ordering.
|
|
|
|
confiform-list
This macro displays your stored data in WYSIWYG view (it also supports filtering and data sorting/ordering).
ConfiForms Form name | formName | The name of the ConfiForm form TableView should use. |
---|---|---|
Form Location page | pageTitle | The location of the page on which the form is defined; leave blank if the form is on the same page. |
Filter | filter | A parameter for selecting records from the dataset; see detailed documentation at ConfiForms Filters and/or in the tutorials. |
Pagination | pager | A parameter to enable displaying records in sets (for example, in groups of 1, 25, 50, 100, or 200 per page); if not configured then all stored records are shown. |
Ordering/Sorting | sort | See detailed documentation at Sorting in ConfiForms and/or in the tutorials. |
CSS styles | css | Use this parameter to customize CSS styling for the table to be generated; to apply a CSS class prefix the ruleset with 'class:' |
confiform-card
This macro displays your stored data as a vertical table (or card) with instant search, filtering, and data sorting/ordering.
ConfiForms Form name | formName | The name of the ConfiForm form that CardView should use. |
---|---|---|
Form Location page | pageTitle | A parameter to store the page where the form has been defined; this should be left blank if the form is defined on the same page |
Filters | filter | See detailed documentation at ConfiForms Filters and/or in the tutorials. |
Ordering/Sorting rules | sort | See detailed documentation at Sorting in ConfiForms and/or in the tutorials. |
Instant search | enableSearch | Adds a search input field above the table to enable quick search and filtering of stored data. |
Enable export | export | This parameter provides a way for non-administrative users to download the returned data in CSV, XML, or JSON formats. While the form's administrative users can always export ConfiForms data with the administrative interface, they should enable data export for non-administrative users with the 'Allow data export' parameter in the ConfiForms form macro. |
Pagination | pager | A parameter to enable displaying records in sets (for example, in groups of 1, 25, 50, 100, or 200 per page); if not configured then all stored records are shown. |
Scrollable tables | wrapped | This parameter provides scroll bars for larger tables by applying CSS style rules. |
CSS styles | css | Use this parameter to customize CSS styling for the table to be generated; to apply a CSS class prefix the ruleset with 'class:' |
confiform-calendar
This macro displays your stored data in a calendar view.
Name of the field to use as a grouping field fro calendar | groupingFieldName | Must be of type Date/Datetime |
---|---|---|
ConfiForms Form name | formName | The name of the ConfiForm form that CardView should use. |
Form Location page | pageTitle | A parameter to store the page where the form has been defined; this should be left blank if the form is defined on the same page |
Filters | filter | See detailed documentation at ConfiForms Filters and/or in the tutorials. |
Ordering/Sorting rules | sort | See detailed documentation at Sorting in ConfiForms and/or in the tutorials. |
CSS styles | css | Use this parameter to customize CSS styling for the table to be generated; to apply a CSS class prefix the ruleset with 'class:' |
confiform-field
This macro defines a field to be displayed within the ConfiForms TableView, ListView, or CardView macros
Field name | fieldName | The name of the field defined on the form referenced. The macro's preview mode displays the field names stored within the form. The ConfiForm metadata fields are available always as well (see above). |
---|---|---|
Field label | withLabel | The label from the ConfiForms field definition will be added as a prefix before the field value. |
Hide if empty | hideIfEmpty | Use this parameter in order to conceal a field when its stored value is blank, as in ListView or CardView, for example. |
CSS styles | css | This parameter provides a way to apply CSS styles (for example: color:red; border:1px) to the field. Styles will be applied on stored values on output. |
confiform-ifttt
This macro defines the integration rules for ConfiForms forms and is to be placed inside ConfiForms Form macro body. The macro body is used as the message body, task content, javascript snippet, page content, or request content, depending on the action type selected.
The macro body completely supports referencing records, including the record owner as [owner], the record modifier as [modifier], and any record field as [entry.FIELD_NAME]. The body can include complex types; see "Subject for email / title for page / url for request" below for details.
This is used when referencing a smart classifier field, and it can access all the standard fields, plus additional fields defined in the ConfiForms entry:
id - the record id, unique for every saved record: [entry.FIELD_NAME.id]
ownedBy - the username of the user who owns the record (and can fully control it): [entry.FIELD_NAME.ownedBy]
ownedByName - the full name of the user who owns the record: [entry.FIELD_NAME.ownedByName]
createdBy - the username of the user who has created the record (admin users can create records for other users): [entry.FIELD_NAME.createdBy]
createdByName - the full name of the user who has created the record: [entry.FIELD_NAME.createdByName]
created - the timestamp when the record was created: [entry.FIELD_NAME.created]
dateCreatedFormatted - a formatted way to see the timestamp for a created record: [entry.FIELD_NAME.dateCreatedFormatted]
As well as other, non-standard fields defined in the ConfiForms entry: [entry.FIELD_NAME.FIELD_NAME]
In order to reference fields to create the email body, a page template, and the data to send to another service, use either the ${} notation or the notation above, using [entry.FIELD_NAME]. Both methods are supported. See detailed example at Using IFTTT macro for integrations.
See also Virtual functions
Use this to specify the sender when configuring a "Send Email" action, or to specify the page to be used as a parent page for a "Create Page" action.
Warning |
---|
Important: the "Create ConfiForms Entry" action does not support propagation of further "Create ConfiForms Entry" actions. This is to avoid infinite loops (an entry creates an entry in another form using IFTTT macro, which creates another entry in the first form, and so on). |
confiform-table-merger
This ConfiForms helper macro merges TableView results.
This macro takes RICH TEXT as an input to define which fields (ConfiForms Field macros) to display and which tables to merge (in the ConfiForms TableView macros). It supports expressions which can be used when aggregating the data. Learn more in TableView Merger examples.
Filter | filter | Select records based on this configuration; see detailed documentation at ConfiForms Filters and/or in the tutorials. |
---|---|---|
Ordering/Sorting | sort | Rules for ordering or sorting entries in the dataset; see detailed documentation at Sorting in ConfiForms and/or in the tutorials. |
Enable export | export | This parameter provides a way to download returned data in CSV, XML and JSON formats. Admin users can always export ConfiForms data with the administrative interface. For non-admin users, the form's owner should enable support for data export via 'Allow data export' in the ConfiForms form macro. |
Pagination | pager | A parameter to enable displaying records in sets (for example, in groups of 1, 25, 50, 100, or 200 per page); if not configured then all stored records are shown. |
Striped table rendering | withHighlighting | This parameter enables highlighting alternate rows in a table. |
For examples, see the documentation in Merge and aggregation for ConfiForms and for advanced techniques, see Advanced aggregations in TableView Merger. |
confiform-field-definition-rules
This macro configures how ConfiForms Field Definitions are related. It supports creating complex relationships between form fields, based on selections, values entered, and so on. To be used inside the ConfiForms Form macro to define rules for Field Definitions.
Field name | actionFieldName | The name of the field to be tracked. |
---|---|---|
Action | action | Action to perform
|
Condition | condition | This parameter defines the condition to be met in order for the action to be executed; it uses the same syntax as in filters; and the scope is the current entry/record. |
Actionable field name | fieldName | When the 'Show/Hide field' action is used, this parameter specifies which fields are affected (can specify a list of comma-separated field names to affect many fields at once). |
Values to be set | values | When the 'Set value' (or 'Set value if empty') action is configured, this parameter specifies which fields and values are to be set. Values are set as key-value pairs, separated by & (as request parameters), where the ''key'' is the field name, and the ''value'' is the entry to be set. |
confiform-field-css
The macro to use to display fields based on their values. To be used inside the ConfiForms TableView, ListView, or CardView macros.
Field value or expression to match | condition | This parameter accepts values or expressions, similar to filters (see the detailed documentation on filters: ConfiForms Filters). The scope for filtering is the whole dataset and depends on the container macro in which this macro is used as the dataset is passed from the container macro. |
---|---|---|
Field name | fieldName | The name of the field to which the CSS styling rule(s) should be applied; if left empty, the style is applied to the row. |
Conditional CSS | css | This parameter accepts valid CSS styles, separated by semicolon (for example: color:red;border:1px). Styles will be applied to a field (if given) or on a row when used within a table (a CSS container div is used when in ConfiForms ListView) if the field name is not set. |
confiform-entry-viewer
The macro to use when you need to show all the fields for the stored entity in a readonly pop-up dialog.
Field name | fieldName | Name of the field defined on the form. Leave empty if you want to use just a static caption. See parameter below |
---|---|---|
Caption/label to use | buttonLabel | Static label to use for viewer field |
Render as | type | The control can be rendered as:
|
Visibility | restrictions | This parameter accepts a comma-separated list of groups and users to which this field will be visible. Leave this parameter blank if there are no restrictions. |
Hide control when stored data matches this criteria | hideIfMatches | Current ConfiForms entry stored by the form referenced will be concealed when the items in this parameter are matched in the entry. The control itself will be hidden when the condition/filter given is met, and this parameter uses the same syntax as in filters . |
CSS styles | css | This parameter provides a way to apply CSS styles (for example: color:red; border:1px) to the field. Styles will be applied on stored values on output. |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ConfiForms Field Definition Rulesconfiform-field-definition-rules | This macro configures how ConfiForms Field Definitions are related. It supports creating complex relationships between form fields, based on selections, values entered, and so on. To be used inside the ConfiForms Form macro to define rules for Field Definitions.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
CSS Rules for ConfiForms Fieldsconfiform-field-css | The macro to use to display fields based on their values. To be used inside the ConfiForms TableView, ListView, CalendarView, CleanView or CardView macros.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ConfiForms View Control (EntryViewer)confiform-entry-viewer | The macro to use when you need to show all the fields for the stored entity in a readonly pop-up dialog.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ConfiForms IFMatches View Helperconfiform-ifmatches | The macro helps you to show the content blocks based on the field values in ConfiForms records (to be used inside the ListView or CalendarView)
Use macro body to put the content you want to show/hide depending on the specified condition | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ConfiForms Dynamic Filterconfiform-entry-filter | The macro helps you to create dynamic filters for your ConfiForms views.
Use macro body to create a custom layout for your filter control, just same as ConfiForms Registration Control macro. Also expects ConfiForms Field macros referencing a form to be present in the macro body. When macro body is blank / empty then standard card-style layout is used and all form fields are set as filtering fields | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ConfiForms LiveView macro confiforms-live-view | See documentation and examples on the following page - Using ConfiForms LiveView macro |
...
from IFTTT macro body |
|
from IFTTT macro title parameter | [entry.FIELD_NAME] |
ConfiForms Registration Control, redirectURL parameter | [entry.FIELD_NAME] |
in Calculated/Formula field, when constructing an expression | [entry.FIELD_NAME] |
...
Info | ||
---|---|---|
| ||
Children Display |
---|