Page 1 of 2. Showing 17 results (0.286 seconds)
Why do I see an extra button with + sign on my form and ownedBy field
The question been asked many times, especially by the new users of ConfiForms add-on for Confluence. image2017-8-31 9:55:6.png And also the related question - why I see this strange button on my page? image2017-8-31 9:55:30.png Both elements are special tools visible ONLY to administrators of the form. Not visibleREST API for ConfiForms CLOUD
": 1541783367283, "id": "5643297d-8bfd-4bf5-b8b6-ef102efe737a", "fields": { "t": "ve", "h": "1541783367347" }, "ownedBy … ", "fields": { "t": "vew", "h": "1541783823321" }, "ownedBy": "<account_id>" }, { "recordId": 2, "createdByConfluence page permissions and ConfiForms
(by default, but could be overwritten). Each record in ConfiForms has an ownedBy user multi-select field (part of metadata fields Documentation). Which can be used … creator of the entry will loose his edit rights to the entry if the owner is altered (ownedBy field) stored data is visible to a user if he has accessConfiForms FAQ
with + sign on my form and ownedBy field Why do I see a "+" button on my form? This is because you are the administrator of the form and allowed to see some metadata and create records on someones behalf. Ordinal users will not see this button. Also see: Why do I see an extra button with + sign on my form and ownedByHow to setup a webservice backed field in AssetForms
", "fields": { "name": "AssetForms for Jira", "available": "[\"cloud\"]" }, "ownedBy": "557058:49c2eeaf-b72c-4e4d-86a7-97c1a77b50b6 … -a605-c6d14dd7d2df", "fields": { "name": "ConfiDoc. Viewer for SQL, XML, JSON, CSV", "available": "[\"server\"]" }, "ownedByData Export tricks and hints
, "class": "fields", "mytf": "hello export", "mydf": 1 }, "ownedBy": "sash" }, { "recordId": 2 … ": { "mydate": 1465272000000, "class": "fields", "mytf": "confiforms tutorial", "mydf": 3 }, "ownedByRelease Notes
You cannot downgrade from version 2.x to version 1.x automatically (without manually re-importing datasets with recovery APIs) Upgrading from 1.x to 2.x is done for you automatically, with data migration. See release notes for the version 2.0.1 We advise you to take extra care with upgrading to version 2.x+ from 1.xEnsuring form non-admin users can enter only one record
with the following settings validate-one-entry-prop1.png Condition is defined as follows: ownedBy:[entry.ownedBy] AND _count:>1 AND _user.userInSecurityGroup … -bfc2-4b3c-9158-d0df83c6dce0" ac:name="confiform-field-definition-rules" ac:schema-version="1"> <ac:parameter ac:name="condition">ownedBy:[entry.ownedByShopping cart like form storage format
> <ac:parameter ac:name="title">item=[entry.item]&count=[entry.count]</ac:parameter> <ac:parameter ac:name="extras2">ownedBy:[entry._user]</ac:parameter … ac:name="action">Delete ConfiForms Entry</ac:parameter> <ac:parameter ac:name="event">onCreated</ac:parameter> <ac:parameter ac:name="title">ownedByAccessing field values and properties
] Deprecated, use [entry._user] current record owner (ownedBy field) or Anonymous (when user is "Anonymous") [modifier] [user] Deprecated, use [entry._user