Page 6 of 15. Showing 149 results (0.338 seconds)
ConfiForms app for creating forms in Confluence
business data can be viewed in tables, as lists, as cards or in combinations. Data can be merged and aggregated, and views can be customized with CSS as needed … with the Confluence security system, using its permissions and access restrictions. You control who can access and edit your ConfiForms data, with fine-grained controlUsing ConfiForms Form Filter Control macro
and choose the "view" macro you want to connect it to, and set the filter ID. Choose the name you want, but remember to put the same value in the "view" macro, for the same "Filter ID" parameter. filter-control-3.png This links the view macro with a filter control macro. Now put a view macro on the same page - couldUsing Field Definition Rule to request data from JIRA and set it to ConfiForms fields
this in view mode: image2016-9-27 10:51:41.png Same form in edit mode: image2016-9-27 10:52:25.png And it's storage format <ac:structured-macro ac:macro-idUsing Confluence templates with ConfiForms and avoid configuration duplication
, but will be included as-is This gives us the unified view of the form in the page created, email sent and when user fillins the form image2016-5-7 10:12:48.png … > <span> <ac:structured-macro ac:macro-id="4ed7249e-7ba0-4b5d-9e66-9ad7e4c624f1" ac:name="confiform-entry-edit" ac:schema-version="1Using ConfiForms Field Definition Rules macro to reduce number of choices in a dropdown field based on the value selected in another field
Then form in the view mode looks like this image2016-9-2 14:39:53.png And this is how it looks in the design mode image2016-9-2 14:40:23.png Let's see how the 2 … a "smart" field, a "smart" dropdown) In the edit mode the form looks exactly the same as in the 1st version. But the difference is in how the "choices" fieldBest practices on how to set up pages with ConfiForms
understand the differences between definitions and views and get yourself familiar with ConfiForms macros, see ConfiForms app detailed view over the plugin macros Have one page per form (definition) Have views (TableView, CardView, etc) and even Form views (Registrations Control macros) on separate pages. Split from pagesUsing and configuring ConfiForms Dynamic Filter Control
it takes all the fields from the form and present them in a card view. You can easily change the layout of this, see below The macro has been renamed from … to * (wildcard) image2016-7-8 14:8:18.png But it does not work without a "view"... without "views" macros, such as CalendarView, ListView, TableView or CardViewData Export tricks and hints
Export formats ConfiForms provides a way to export data in 4 different formats (or in 6 if you count flattened views as separate types) CSV (+flattened view) - comma separated values XLS (+flattened view) - Microsoft Excel format JSON - JSON format XML - dataset exported in an XML format First 2 are for endVirtual functions
values in ConfiForms directly in teh views [entry.myfield.formatLink(https://google.com?q=)] will create a <a href="https://google.com?q=<VALUE_OF_MY_FIELD … by ,) obscure Hides the value behind the given mask pwd.obscure(********|click to view) Will create something like obscure-password-demo.png ClickingWhy do I see an extra button with + sign on my form and ownedBy field
and ConfiForms The "+" button shows you the metadata fields for the record you are viewing The button with a "cog wheel" and the name of your form provides an auto-generated admin view over your stored data, and also quick links to Migration and Recovery API and Import API These UI elements are NOT VISIBLE for ordinal