...
ConfiForms - Data Forms & Workflows app for Atlassian Confluence
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).
??: does "record" mean the data submitted (or saved) through a form, or the form itself? Does 'register' mean "save" (or "submitted"), or is "registration" a different process from submitting (saving) data records?
See more on Confluence page permissions and ConfiForms
Each record stored Each record registered 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 register 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.
Each record in ConfiForms has the following associated metadata:
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 |
---|
|
...
|
...
|
...
|
...
|
...
|
...
|
...
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:
- TableView macro
- ListView macro
- CardView macro
Quick tips
- Each form has a name and belongs to a page. Use the form's name and the Confluence page where the form is configured to reference a ConfiForms Form
- To define the form, use the ConfiForms Form and Field Definition macros
- To enable registrations and display the form, use the ConfiForms Registration Control macro
- To display the form with its own layout , use the ConfiForms Registration Control macro body as a container for the form's design, placing ConfiForms Field macros in the container that define the form's fields
- To send email from ConfiForm, use an IFTTT macro placed inside the ConfiForms Form macro
- To display saved data, use the ConfiForms TableView, ListView, or CardView macro
- To customize the output , use the CSS rules for ConfiForms Fields macro
- To configure dependent fields and relations between fields, use the ConfiForms Field Definition Rules macro
- To aggregate and merge the data from different ConfiForms Forms, use the ConfiForms TableView Merger macro
Macro documentation
|
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:
- TableView macro
- ListView macro
- CardView macro
- CalendarView macro
- PlainView macro - when you need just values from ConfiForms and want to construct you tables/HTML widgets yourself (to be used in conjunction with HTML macro, for example; and using [entry.FIELD_NAME] notation to reference field values )
- CleanView - similar to ListView, with less capabilities but with a lot cleaner HTML generated. Useful for designing own macros (with user macros) and mising it with HTML and other macros. Supports macros insides it's body
- ValueView macro - is self contained and shows the field value directly (no need to use "ConfiForms Field macro")
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 |
Our Backlog
ConfiForms (FormView) Registrations Control | ||||||
---|---|---|---|---|---|---|
| ||||||
Quick tips
- Each form has a name and belongs to a page. Use the form's name and the Confluence page where the form is configured to reference a ConfiForms Form
- To define the form, use the ConfiForms Form and Field Definition macros
- To enable registrations and display the form, use the ConfiForms Registration Control macro
- To display the form with its own layout , use the ConfiForms Registration Control macro body as a container for the form's design, placing ConfiForms Field macros in the container that define the form's fields
- To enable data edits use ConfiForms Edit Controls with ConfiForms TableView, ListView, CalendarView or CardView macros
- To add convenient viewer to your data use ConfiForms Entity Viewer with ConfiForms TableView, ListView, CalendarView or CardView macro
- To send email from ConfiForm, use an IFTTT macro placed inside the ConfiForms Form macro
- To display saved data, use the ConfiForms TableView, ListView, CalendarView, CardView or ValueView macro
- To customize the output , use the CSS rules for ConfiForms Fields macro
- To configure dependent fields and relations between fields, use the ConfiForms Field Definition Rules macro
- To aggregate and merge the data from different ConfiForms Forms, use the ConfiForms TableView Merger macro
Take a look also at conceptual view over all macros from ConfiForms app - ConfiForms app detailed view over the plugin macros
Excerpt Include | ||||
---|---|---|---|---|
|
Macro documentation
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 Form
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. |
Lock form | locked | Use this flag when the ConfiForm should be locked to stop additional records being 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 to records owned by the user will be visible to this user. Admin users will still have access to all the 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. |
ConfiForms Field Definition
confiform-field-definition
The macro to use inside the ConfiForms Form macro to define the form's fields, their types, and behavior.
type
??: Are registrations/enrollments record submissions or different operations?
Should unlinked type names such as "Enroll button", "Formula", and "Masked Text" be links, and if so to what?
??: does the "password" type obscure entered characters in the form? If not, what makes this type different from a normal field?
??: Should these be broken out into separate rows with corresponding version and definitions? If not, how should we differentiate among them?
??: does the User field type provide ajax-style pre-selection based on what the user types in?
The field's type which defines how data can be entered in the field (datepickers for dates, dropdowns, etc.) according to these definitions:
Type | Compatibility | Description | ||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Text | 4.3+ | A simple text input field. | ||||||||||||||||||||||||||||||||||||||||||||
Autolink | 4.3+ | This type creates automatic links to resources based on a defined pattern. When used with an IFTTT macro to create pages, autolinks can reference the record owner as [owner]; the record modifier, as [modifier]; and any record field as [entry.FIELD_NAME] (except entry.id , which is not available when a record is about to be created) | ||||||||||||||||||||||||||||||||||||||||||||
Autonumber | 4.3+ | This type makes the field's value an auto-incremented number assigned automatically to each record. You can control how the number is displayed by using a mask (prefix) and an initial number. See Text masks and masked input. | ||||||||||||||||||||||||||||||||||||||||||||
Autopage | 4.3+ | This field type records the source page where the record was submitted. | ||||||||||||||||||||||||||||||||||||||||||||
Calculated | 4.3+ | This type sets the value for the field based on an expression which can reference record owner as [owner]; record modifier, as [modifier]; any record field as [entry.FIELD_NAME]. Important: the value is calculated only when an entry is created. See the "Formula" field type for a field which is recalculated on each edit. See Supported math operators and functions. | ||||||||||||||||||||||||||||||||||||||||||||
Checkbox | 4.3+ | Display the field as a checkbox. | ||||||||||||||||||||||||||||||||||||||||||||
Checkbox group | 4.3+ | Displays the field's options as a group of checkboxes. | ||||||||||||||||||||||||||||||||||||||||||||
Date | 5.0+ | This type provides a datepicker that stores data in the format specified in Confluence's general settings for Date Format. | ||||||||||||||||||||||||||||||||||||||||||||
Datetime | 5.0+ | A datepicker with time control to store data in the format specified in Confluence's general settings for Date Time Format. | ||||||||||||||||||||||||||||||||||||||||||||
Drawing canvas | 4.3+ | A field type for capturing simple drawings such as 'wet signatures,' for example. | ||||||||||||||||||||||||||||||||||||||||||||
Dropdown | 4.3+ | This field type creates a drop-down list (or combobox) for capturing user input. | ||||||||||||||||||||||||||||||||||||||||||||
Dynamic Dropdown | 4.3+ | This one offers a dynamic drop-down list (or combobox) in which the values can be pre-defined or referenced from another form; it includes an option for users to enter their own values. | ||||||||||||||||||||||||||||||||||||||||||||
Enroll button | 5.0+ | This field type enables one-click registrations and enrollments. | ||||||||||||||||||||||||||||||||||||||||||||
File | 4.3+ | This type provides a way to upload files and images. Uploads will be stored as attachments on the page where the ConfiForms form is defined. | ||||||||||||||||||||||||||||||||||||||||||||
Formula | 4.3+ | This field type sets the value for the field based on an expression which can reference the record owner as [owner], a record modifier as [modifier]; and any record field as [entry.FIELD_NAME]. Important: this value is calculated every time an entry is updated (and created). See the "Calculated" type if the field should NOT recalculated on each edit. See Supported math operators and functions. | ||||||||||||||||||||||||||||||||||||||||||||
Hidden | 4.3+ | This type provides for a concealed constant value to be stored with the record. | ||||||||||||||||||||||||||||||||||||||||||||
Link | 4.3+ | This field type offers a convenient way to store links to other resources and display them as links. | ||||||||||||||||||||||||||||||||||||||||||||
Masked Text | 4.3+ | This type provides a way to mask (or constrain the format of characters entered) in a text field. For example, a mask of 00/00/0000 will format the entry in this way: 23/12/2014. See Text masks and masked input to learn more about defining a mask. | ||||||||||||||||||||||||||||||||||||||||||||
Multiselect | 5.1+ | This type stores multiple values for the field. | ||||||||||||||||||||||||||||||||||||||||||||
JIRA issue | 4.3+ | This field type provides a means to reference a JIRA issue. It requires an application link between Confluence and JIRA. | ||||||||||||||||||||||||||||||||||||||||||||
Page/Blog post | 4.3+ | This type permits the field to reference a Confluence page or blog post. | ||||||||||||||||||||||||||||||||||||||||||||
Password | 5.0+ | A type for passwords which obscures the characters being entered. | ||||||||||||||||||||||||||||||||||||||||||||
Radio group | 4.3+ | 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. | ||||||||||||||||||||||||||||||||||||||||||||
Section | 4.3+ | This is a section placeholder to separate fields into groups on the form. | ||||||||||||||||||||||||||||||||||||||||||||
Simple date | 4.3+ | This type offers 3-part drop-down lest (year, month, and day) for easy date selection. | ||||||||||||||||||||||||||||||||||||||||||||
Smart classifier | 4.3+ | This sophisticated field type allows users to enter data based on a stored structured dataset and the deep structure can be defined as needed. | ||||||||||||||||||||||||||||||||||||||||||||
4.3+ Smart-multiselect 5.1+ | This type provides a means for referencing the data from other ConfiForm forms, either another form's drop-down values, or records stored directly (see the flag 'Reference to values'). | |||||||||||||||||||||||||||||||||||||||||||||
Status | 5.0+ | 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:
| ||||||||||||||||||||||||||||||||||||||||||||
Textarea | 4.3+ | This type provides a textarea for user input. | ||||||||||||||||||||||||||||||||||||||||||||
User | 4.3+ | This field type enables a reference to a Confluence user. | ||||||||||||||||||||||||||||||||||||||||||||
User (multiselect) | 5.1+ | Like the User type, this one allows seletion of multiple users. | ||||||||||||||||||||||||||||||||||||||||||||
WYSIWYG | 5.0+ (on 4.3 this controls is shown as textarea) | This field type providea a simple editor that supports basic formatting styles. |
* The Compatibility column shows the Confluence version number with which this field type is compatible.
ConfiForms Registration Control
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 Edit Controls
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. |
Conditional cealment parameters | 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 . |
ConfiForms TableView
confiform-table
The macro to display stored data as a table, with instant search, filtering, and data sorting/ordering.
ConfiForms Form name | formName | The name of the ConfiForm form that TableView will use. |
---|---|---|
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. |
Filter | filter | The filter to be applied to the stored dataset; see detailed documentation at ConfiForms Filters and/or in the tutorials. |
Ordering/Sorting rules | sort | Rules for ordering and sorting the returned dataset; see detailed documentation at Sorting in ConfiForms and/or in the tutorials. |
Enable instant search | enableSearch | This parameter adds a search input field above the table to enable quick searching and filtering of the 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:' |
Striped table rendering | withHighlighting | This parameter enables highlighting alternate rows in a table. |
ConfiForms ListView
confiform-list
Macro to visualize your stored data in WYSIWYG view (also supports filtering and data sorting/ordering)
ConfiForms Form name | formName | Name of the ConfiForm form TableView should use |
---|---|---|
Page name where the form is defined | pageTitle | Leave blank if the form is defined on the same page |
Filter to apply on entries dataset | filter | 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 rules to apply on entries dataset | sort | See detailed documentation at Sorting in ConfiForms and/or in the tutorials. |
CSS styles for ListView (div) | css | Use this parameter to customize CSS styling for the table to be generated; to apply a CSS class prefix the ruleset with 'class:' |
ConfiForms CardView
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 | 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:' |
ConfiForms Field
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. |
ConfiForms IFTTT
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, 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.
- onCreated - when a new record is created
- onModified - when a record is modified
- onDeleted - when a record is deleted
- Send Email - Send email to the list of participants, defined below
- Create Page - Create a page based on a given template
- Make request - Performs an HTTP request (GET or POST, depending on the macro body).
- Send Notification - Send a Confluence notification
- Create ConfiForms Entry - create a ConfiForms entry in another form
allows parameters and substitutions which can be constructed dynamically, including references to the record owner as [owner], the record modifier as [modifier], and any record field as [entry.FIELD_NAME].
Complex fields (such as of type page/blogpost or user) are also supported.
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]
username: [entry.FIELD_NAME.username]
email: [entry.FIELD_NAME.email]
spaceKey: [entry.FIELD_NAME.spaceKey]
id: [entry.FIELD_NAME.id]
version: [entry.FIELD_NAME.version]
as well as other simple Page properties.
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.
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). |
ConfiForms TableView Merger
confiform-table-merger
This ConfiForms helper macro merges TableView results
Macro takes RICH TEXT as an input, and you need to define which fields (ConfiForms Field macros) to show and which tables to merge (ConfiForms TableView macros). There is a support for expressions to be used when aggregating your 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. |
ConfiForms Field Definition Rules
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 with a list of comma-separated field names. |
Values to be set | values | When the 'Set value' 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. |
CSS Rules for ConfiForms Fields
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. |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
How to reference a ConfiForms field (also Accessing field values and properties)
...
:
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 | ||
---|---|---|
| ||
More detailed documentation bits
Children Display |
---|