API

System APIs

PUT system/application-versions/{applicationVersionId}

Update an application version

HTTP method PUT
URI https://api.rambase.net/system/application-versions/{applicationVersionId}
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {applicationVersionId}
String, regular expression: ^[0-9]+[(\.)]?[0-9]*[(\.)]?[0-9]*$
Successful HTTP status code 200
API resource identifier 2066, 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.

Format:
1
<ApplicationVersion
ApplicationVersion

This field is optional.

>
2
     <ApplicationMatch
ApplicationMatch

Matching Keyword

This field is optional.

>{String}</ApplicationMatch>
3
     <CustomFieldOrder
CustomFieldOrder

It is possible for a customer to rearrange the fields within a component. If they choose to do so for one or more of the components in this application, the fieldorder will contain a json structure that will keep information about the field order they have selected.

This field is optional.

>
4
          <FieldOrder
FieldOrder

A json structure describing the field order

This field is optional.

>{String}</FieldOrder>
5
     </CustomFieldOrder>
6
</ApplicationVersion>
1
{
2
     "applicationVersion
ApplicationVersion

This field is optional.

": {
3
          "applicationMatch
ApplicationMatch

Matching Keyword

This field is optional.

": "{String}",
4
          "customFieldOrder
CustomFieldOrder

It is possible for a customer to rearrange the fields within a component. If they choose to do so for one or more of the components in this application, the fieldorder will contain a json structure that will keep information about the field order they have selected.

This field is optional.

": {
5
               "fieldOrder
FieldOrder

A json structure describing the field order

This field is optional.

": "{String}"
6
          }
7
     }
8
}

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.

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. Fields colored in grey is expandable fields.

Please note that some fields may be removed from the response, based on user roles/duties/permissions.

Format:
1
1

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 107080 HTTP 403 You have only admittance to your own objects
Error 101620 HTTP 400 You have to create your own edit version of the application version before you can edit it.