RamBase REST APIs
Create filter for given automated flow
| HTTP method | POST |
| URI | https://api.rambase.net/system/automated-flows/{automatedFlowId}/filters |
| Supported formats | Xml, Html, Json (ex. $format=json) |
| - URI parameter {automatedFlowId} |
Automated flow identifier
Integer, minimum 100000 |
| Successful HTTP status code | 201 |
| API resource identifier | 4796, version 1 |
The following body must be added to the request. Mouse over fieldnames for description and other useful information about the fields. Note that fields in bold are required/mandatory.
Field
Required/mandatory field
Automated flow filter field
>{String}</Field>Operator
Required/mandatory field
Automated filter operator
Applicable domain values can be found here
>{String}</Operator>Condition
Required/mandatory field
Automated flow filter condition
>{String}</Condition>Field
Required/mandatory field
Automated flow filter field
": "{String}",Operator
Required/mandatory field
Automated filter operator
Applicable domain values can be found here
": "{String}",Condition
Required/mandatory field
Automated flow filter condition
": "{String}"The query string is placed after the resource URL, seperated with a questionmark (?). The query string is composed of a series of query parameters with values. See the page about query parameters on how to use these parameters.
| $access_token String, optional | After successful login you get an access token which needs to be provided in all API requests. Even though it is possible to pass this token as query parameter, we recommended passing it using the HTTP request header as described in Authorization. Note that all access tokens have an expiration time. |
| $db String, optional | Set the database/company for the request |
| $useMinimumVersion Integer, optional | Used to run a new version of an API resource when your API client is running a deprecated API resource. See the Breaking changes page for more information. |
| $showDomainDescriptions Boolean, optional | Set to "true" to include domain descriptions for fields using domain values. See the Domain values page for more information. Default value is false. |
| $lang String, optional | Specifies the language used in the response, following the 3-letter ISO-639-1 [lll] |
Read more about filters and sorting on how to use filter parameters and named filters.
Read more about filters and sorting on how to use sortable parameters
Requesting this resource will yield the following response. Mouse over fieldnames (or fieldgroups) for descriptions and other useful information about the fields.
Please note that some fields may be removed from the response, based on user roles/duties/permissions.
AutomatedFlowFilterId
Automated flow filter identifier
>{Integer}</AutomatedFlowFilterId>Field
Automated flow filter field
>{String}</Field>Operator
Automated filter operator
Possible domain values can be found here
>{String}</Operator>Condition
Automated flow filter condition
>{String}</Condition>AutomatedFlowFilterId
Automated flow filter identifier
": "{Integer}",Field
Automated flow filter field
": "{String}",Operator
Automated filter operator
Possible domain values can be found here
": "{String}",Condition
Automated flow filter condition
": "{String}"
List of available operations/actions for this resource.
See the operations documentation for more information about API operations.
Possible error codes the response might return:
| Error 101013 HTTP 404 | Sub-module not found |
| Error 106417 HTTP 404 | Automated flow filter not found |