API

System APIs

GET system/setting-definitions/{settingDefinitionId}

System setting definition details for the provided identifier

HTTP method GET
URI https://api.rambase.net/system/setting-definitions/{settingDefinitionId}
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {settingDefinitionId} System setting definition identifier
Integer, minimum 100000
Successful HTTP status code 200
API resource identifier 3021, version 4

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
1

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.

$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]
$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
$format String, optional Set the format of the response to use for the request. Accepted values are "xml", "html", "jsonstream", "json"
$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.
$select String, optional Use to define the fields to return in the response. Accepts a comma-separated list of field names. See the Expand and select page for more information.
$expand String, optional Use to include output fields that are not returned by default in the response. Accepts a comma-separated list of expandable field names. See the Expand and Select 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
<SystemSettingDefinition>
2
     <SystemSettingDefinitionId
SystemSettingDefinitionId

System setting definition identifier

>{Integer}</SystemSettingDefinitionId>
3
     <Status
Status

Status of system setting definition

Possible domain values can be found here

>{Integer}</Status>
4
     <Key
Key

Setting name used to reference the setting

>{String}</Key>
5
     <Name
Name

Short name/description of the setting definition

>{String}</Name>
6
     <TranslatedName
TranslatedName

Name translated to selected language. If no translation exists for the given langauage, english name will show.

This field is greyed out because it is an expandable field. You have to add $expand=TranslatedName in your request URI to get this field

>{String}</TranslatedName>
7
     <Description
Description

Descrtiption of the setting definition

>{String}</Description>
8
     <TranslatedDescription
TranslatedDescription

Description translated to selected language. If no translation exists for the given langauage, english description will show.

This field is greyed out because it is an expandable field. You have to add $expand=TranslatedDescription in your request URI to get this field

>{String}</TranslatedDescription>
9
     <DefaultValue
DefaultValue

Default value if setting not set for system

>{String}</DefaultValue>
10
     <DataType
DataType

Allowed values for setting. Used for validation of input from user.

>{String}</DataType>
11
     <MinimumValue
MinimumValue

For data type integer or decimal a minimum value can be specified, e.g. if a value range is allowed.

>{Decimal}</MinimumValue>
12
     <MaximumValue
MaximumValue

For data type integer or decimal a maximum value can be specified, e.g. if a value range is allowed.

>{Decimal}</MaximumValue>
13
     <IsRequired
IsRequired

Flag if setting is required/must be set before using system. If this is a sub-setting, this settings must be set when the parent setting is turned on. The user must activate this setting (a system setting value must exist for this setting). If a default value is also specified, that will actually be a suggested value, the setting must still be activated.

>{Boolean}</IsRequired>
14
     <NumberOfChildSettings
NumberOfChildSettings

Number of system setting definitions this setting is parent for.

This field is greyed out because it is an expandable field. You have to add $expand=NumberOfChildSettings in your request URI to get this field

>{Integer}</NumberOfChildSettings>
15
     <Module>
16
          <ModuleId
ModuleId

Module identifier

>{Integer}</ModuleId>
17
          <Name
Name

Name of the module

>{String}</Name>
18
          <ModuleLink
ModuleLink

Module reference

>{String}</ModuleLink>
19
     </Module>
20
     <ParentSystemSettingDefinition>
21
          <SystemSettingDefinitionId
SystemSettingDefinitionId

System setting definition identifier

>{Integer}</SystemSettingDefinitionId>
22
          <Name
Name

Short name/description of the setting definition

This field is greyed out because it is an expandable field. You have to add $expand=ParentSystemSettingDefinition.Name in your request URI to get this field

>{String}</Name>
23
          <SystemSettingDefinitionLink
SystemSettingDefinitionLink

System setting definition reference

>{String}</SystemSettingDefinitionLink>
24
     </ParentSystemSettingDefinition>
25
     <DomainValueList>
26
          <Object
Object

Object/archive/context of the DOV

>{String}</Object>
27
          <Field
Field

Fieldname of the DOV

>{String}</Field>
28
     </DomainValueList>
29
     <ViewPermission>
30
          <PermissionId
PermissionId

Permission identifier

>{Integer}</PermissionId>
31
          <Name
Name

Name of the permission

>{String}</Name>
32
          <PermissionLink
PermissionLink

Permission reference

>{String}</PermissionLink>
33
     </ViewPermission>
34
     <UpdatePermission>
35
          <PermissionId
PermissionId

Permission identifier

>{Integer}</PermissionId>
36
          <Name
Name

Name of the permission

>{String}</Name>
37
          <PermissionLink
PermissionLink

Permission reference

>{String}</PermissionLink>
38
     </UpdatePermission>
39
     <Repository
Repository

This field is greyed out because it is an expandable field. You have to add $expand=Repository in your request URI to get this field

>
40
          <IsChanged
IsChanged

Tells whether this object has been changed locally and are ready to be committed to the Repository

This field is greyed out because it is an expandable field. You have to add $expand=Repository in your request URI to get this field

>{Boolean}</IsChanged>
41
          <ChangedBy
ChangedBy

EmployeeId of the employee making the change

This field is greyed out because it is an expandable field. You have to add $expand=Repository in your request URI to get this field

>
42
               <UserId
UserId

User identifier

This field is greyed out because it is an expandable field. You have to add $expand=Repository in your request URI to get this field

>{Integer}</UserId>
43
               <UserLink
UserLink

User reference

This field is greyed out because it is an expandable field. You have to add $expand=Repository in your request URI to get this field

>{String}</UserLink>
44
          </ChangedBy>
45
          <IsPendingDeployment
IsPendingDeployment

Tells whether this object has been changed locally and is ready to be deployed from the Repository

This field is greyed out because it is an expandable field. You have to add $expand=Repository in your request URI to get this field

>{Boolean}</IsPendingDeployment>
46
     </Repository>
47
</SystemSettingDefinition>
1
{
2
     "systemSettingDefinition": {
3
          "systemSettingDefinitionId
SystemSettingDefinitionId

System setting definition identifier

": "{Integer}",
4
          "status
Status

Status of system setting definition

Possible domain values can be found here

": "{Integer}",
5
          "key
Key

Setting name used to reference the setting

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

Short name/description of the setting definition

": "{String}",
7
          "translatedName
TranslatedName

Name translated to selected language. If no translation exists for the given langauage, english name will show.

This field is greyed out because it is an expandable field. You have to add $expand=TranslatedName in your request URI to get this field

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

Descrtiption of the setting definition

": "{String}",
9
          "translatedDescription
TranslatedDescription

Description translated to selected language. If no translation exists for the given langauage, english description will show.

This field is greyed out because it is an expandable field. You have to add $expand=TranslatedDescription in your request URI to get this field

": "{String}",
10
          "defaultValue
DefaultValue

Default value if setting not set for system

": "{String}",
11
          "dataType
DataType

Allowed values for setting. Used for validation of input from user.

": "{String}",
12
          "minimumValue
MinimumValue

For data type integer or decimal a minimum value can be specified, e.g. if a value range is allowed.

": "{Decimal}",
13
          "maximumValue
MaximumValue

For data type integer or decimal a maximum value can be specified, e.g. if a value range is allowed.

": "{Decimal}",
14
          "isRequired
IsRequired

Flag if setting is required/must be set before using system. If this is a sub-setting, this settings must be set when the parent setting is turned on. The user must activate this setting (a system setting value must exist for this setting). If a default value is also specified, that will actually be a suggested value, the setting must still be activated.

": "{Boolean}",
15
          "numberOfChildSettings
NumberOfChildSettings

Number of system setting definitions this setting is parent for.

This field is greyed out because it is an expandable field. You have to add $expand=NumberOfChildSettings in your request URI to get this field

": "{Integer}",
16
          "module": {
17
               "moduleId
ModuleId

Module identifier

": "{Integer}",
18
               "name
Name

Name of the module

": "{String}",
19
               "moduleLink
ModuleLink

Module reference

": "{String}"
20
          },
21
          "parentSystemSettingDefinition": {
22
               "systemSettingDefinitionId
SystemSettingDefinitionId

System setting definition identifier

": "{Integer}",
23
               "name
Name

Short name/description of the setting definition

This field is greyed out because it is an expandable field. You have to add $expand=ParentSystemSettingDefinition.Name in your request URI to get this field

": "{String}",
24
               "systemSettingDefinitionLink
SystemSettingDefinitionLink

System setting definition reference

": "{String}"
25
          },
26
          "domainValueList": {
27
               "object
Object

Object/archive/context of the DOV

": "{String}",
28
               "field
Field

Fieldname of the DOV

": "{String}"
29
          },
30
          "viewPermission": {
31
               "permissionId
PermissionId

Permission identifier

": "{Integer}",
32
               "name
Name

Name of the permission

": "{String}",
33
               "permissionLink
PermissionLink

Permission reference

": "{String}"
34
          },
35
          "updatePermission": {
36
               "permissionId
PermissionId

Permission identifier

": "{Integer}",
37
               "name
Name

Name of the permission

": "{String}",
38
               "permissionLink
PermissionLink

Permission reference

": "{String}"
39
          },
40
          "repository
Repository

This field is greyed out because it is an expandable field. You have to add $expand=Repository in your request URI to get this field

": {
41
               "isChanged
IsChanged

Tells whether this object has been changed locally and are ready to be committed to the Repository

This field is greyed out because it is an expandable field. You have to add $expand=Repository in your request URI to get this field

": "{Boolean}",
42
               "changedBy
ChangedBy

EmployeeId of the employee making the change

This field is greyed out because it is an expandable field. You have to add $expand=Repository in your request URI to get this field

": {
43
                    "userId
UserId

User identifier

This field is greyed out because it is an expandable field. You have to add $expand=Repository in your request URI to get this field

": "{Integer}",
44
                    "userLink
UserLink

User reference

This field is greyed out because it is an expandable field. You have to add $expand=Repository in your request URI to get this field

": "{String}"
45
               },
46
               "isPendingDeployment
IsPendingDeployment

Tells whether this object has been changed locally and is ready to be deployed from the Repository

This field is greyed out because it is an expandable field. You have to add $expand=Repository in your request URI to get this field

": "{Boolean}"
47
          }
48
     }
49
}

Possible error codes the response might return:

Error 101015 HTTP 404 Permission not found