...
Search | Searches and filters ConfiForms entries based on a QUERY (ConfiForms Filters) given |
| /search/{token}/{pageId}/{formName}?q=<QUERY> Supports optional parameters:
| Where QUERY is an expression in ConfiForms Filters format Not providing a "QUERY" ("q" parameter) will match all records | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Delete | Deletes ConfiForms record from the form by id (UUID) |
| /delete/{token}/{pageId}/{formName}/{entryId} | User must have permissions to edit/delete the record. This means ConfiForms cloud system user (com.vertuna.confluence.plugins.confiforms) must have enough permissions to do that. | ||||||||
DeleteBy | Deletes ConfiForms records from the form by given QUERY (ConfiForms Filters) |
| /deleteBy/{token}/{pageId}/{formName}?q=<QUERY> | Where QUERY is an expression in ConfiForms Filters format Not providing a "QUERY" ("q" parameter) will match all records. Use Search to see matching records to see what records will be affected by delete to test your "query" (filtering expression) | ||||||||
Validate | Validates parameters against the rules and field types configured by the form |
| /validate/{token}/{pageId}/{formName}?<FIELDS> | fields are given in a key=value format as any HTTP request parameters | ||||||||
Save / Update | Saves the parameters given as new record in ConfiForms form. Alls the rules are applied before saving according to form configuration. If an ID is provided in the fields set then ConfiForms attempts to update the record by given id with given data |
| /save/{token}/{pageId}/{formName}?<FIELDS> Instead of <FIELDS> parameters added to the request url query string you can use POST method and send over the JSON payload with the structure as follows:
Multi-value fields you can give as JSON arrays
You can also POST a request with multipart/form-data. This comes handy when you want to upload attachments together with record creation. Alternatively you can have a file encoded as base64
Please note that the parameter names must match the field names you have defined in your ConfiForms form | fields are given in a key=value format as any HTTP request parameters
Partial updates are supported. Meaning that you can supply less parameters than the record has (missing fields will not be updated). To set the field value to empty, do supply it as a parameter myfield= (where "myfield" is the name of the field you want to set the empty value for) | ||||||||
Get | Loads ConfiForms record by id (UUID) |
| /get/{token}/{pageId}/{formName}/{entryId} Supports optional parameters:
| 404 if not found | ||||||||
Update specific field by filter | Updates ConfiForms field by query (for each record matching the query) |
| /update/{token}/{pageId}/{formName}?q=<QUERY>&fv=field:value | Where QUERY is an expression in ConfiForms Filters format and "fv" is given in a field:value format, where "field" is the name of the field in ConfiForms record you want to update with "value" | ||||||||
Definition | Returns form configuration |
| /definition/{token}/{pageId}/{formName} | Returns form definition (configuration) 404 if not found |
...