PUT system/applications/{applicationId}/versions/{applicationVersionId}

Update an application version

Note: Log in to check if your API client have access to run this resource
Version: 18
Success HTTP Status Code: 200

Uri parameters

{applicationId} Integer Application version identifier
{applicationVersionId} Integer Unique identifier for an application version

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 is required/mandatory.

Format:
1
<ApplicationVersion
ApplicationVersion

This field is optional.

>
2
     <Type
Type

Type of HTML5 component. Used for widgets.

Applicable domain values can be found here when logged in

This field is optional.

>
{String}</Type>
3
     <Name
Name

Name of application

This field is optional.

>
{String}</Name>
4
     <DescriptiveName
DescriptiveName

Descriptive name of the application

This field is optional.

>
{String}</DescriptiveName>
5
     <Description
Description

The descriptive tag of an application or component

This field is optional.

>
{String}</Description>
6
     <Namespace
Namespace

Namespace of the Application

This field is optional.

>
{String}</Namespace>
7
     <ContentType
ContentType

Content Type

Applicable domain values can be found here when logged in

This field is optional.

>
{String}</ContentType>
8
     <ChangeDescription
ChangeDescription

Version description.

This field is optional.

>
{String}</ChangeDescription>
9
     <LookupKey
LookupKey

Matching Keyword

This field is optional.

>
{String}</LookupKey>
10
     <LookupPriority
LookupPriority

The priority of whitch the application lookup will select applications with the same applicationmatch.

This field is optional.

>
{Integer}</LookupPriority>
11
     <Permission
Permission

Permission to use this application

This field is optional.

>
12
          <PermissionId
PermissionId

Permission identifier

This field is optional.

>
{Integer}</PermissionId>
13
     </Permission>
14
     <RedirectToApplication
RedirectToApplication

This field is optional.

>
15
          <ApplicationId
ApplicationId

Wrapper application. This field holds the Id for the main application. Wrapper Apps are used to have different application match names for the same application (ex: CUS and CUSTOMER)

This field is optional.

>
{Integer}</ApplicationId>
16
     </RedirectToApplication>
17
     <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.

>
18
          <FieldOrder
FieldOrder

A json structure describing the field order

This field is optional.

>
{String}</FieldOrder>
19
     </CustomFieldOrder>
20
</ApplicationVersion>
1
{
2
     "applicationVersion
ApplicationVersion

This field is optional.

":
{
3
          "type
Type

Type of HTML5 component. Used for widgets.

Applicable domain values can be found here when logged in

This field is optional.

":
"{String}",
4
          "name
Name

Name of application

This field is optional.

":
"{String}",
5
          "descriptiveName
DescriptiveName

Descriptive name of the application

This field is optional.

":
"{String}",
6
          "description
Description

The descriptive tag of an application or component

This field is optional.

":
"{String}",
7
          "namespace
Namespace

Namespace of the Application

This field is optional.

":
"{String}",
8
          "contentType
ContentType

Content Type

Applicable domain values can be found here when logged in

This field is optional.

":
"{String}",
9
          "changeDescription
ChangeDescription

Version description.

This field is optional.

":
"{String}",
10
          "lookupKey
LookupKey

Matching Keyword

This field is optional.

":
"{String}",
11
          "lookupPriority
LookupPriority

The priority of whitch the application lookup will select applications with the same applicationmatch.

This field is optional.

":
"{Integer}",
12
          "permission
Permission

Permission to use this application

This field is optional.

":
{
13
               "permissionId
PermissionId

Permission identifier

This field is optional.

":
"{Integer}"
14
          },
15
          "redirectToApplication
RedirectToApplication

This field is optional.

":
{
16
               "applicationId
ApplicationId

Wrapper application. This field holds the Id for the main application. Wrapper Apps are used to have different application match names for the same application (ex: CUS and CUSTOMER)

This field is optional.

":
"{Integer}"
17
          },
18
          "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.

":
{
19
               "fieldOrder
FieldOrder

A json structure describing the field order

This field is optional.

":
"{String}"
20
          }
21
     }
22
}

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.

$db String, optional Set the database to use for the request
$format String, optional Set the format of the response to use for the request. Accepted values are "xml", "json"
$lang String, optional Use to get localized responses. Supported formats are 3-letter ISO-639-1 [lll], 2-letter ISO-639-2 [ll], or a combination of a two-letter language code and a two-letter country code ISO-639-2 and ISO-3166-1 [ll_CC], [ll-CC]
$useMinimumVersion Integer, optional This can be used to test a new version of a resource when your ApiClient is running an older, deprecated, version of a resource. $useminimumversion can be used to test against a newer version of the resource. See the Deprecated APIs page for more information about this.

See the page about filters and sorting on how to use filter parameters and named filters.

See the page 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 102868 HTTP 404 Application version not found
Error 102870 HTTP 400 Application must be in edit status (1) to update
Error 101814 HTTP 404 Employee not found
Error 101015 HTTP 404 Permission not found
Error 100449 HTTP 403 Scope cannot be changed