System APIs
Create a new duty
HTTP method | POST |
URI | https://api.rambase.net/system/duties |
Supported formats | Xml, Html, Json (ex. $format=json) |
Successful HTTP status code | 201 |
API resource identifier | 2090, version 9 |
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.
Name
Required/mandatory field
Name of the duty
>{String}</Name>Description
Description of the duty
This field is optional.
>{String}</Description>RequiredUserLevel
The user level required to have a duty. Only users having the same level or higher can have the duty. Therefore a duty can only be added to roles that have the same user level or higher.
User level (highest level first): Administrator, Partner, User, Portal user
Applicable domain values can be found here
This field is optional.
>{Integer}</RequiredUserLevel>SubModuleId
Required/mandatory field
Submodule identifier
Minimum value: 100000
>{Integer}</SubModuleId>Name
Required/mandatory field
Name of the duty
": "{String}",Description
Description of the duty
This field is optional.
": "{String}",RequiredUserLevel
The user level required to have a duty. Only users having the same level or higher can have the duty. Therefore a duty can only be added to roles that have the same user level or higher.
User level (highest level first): Administrator, Partner, User, Portal user
Applicable domain values can be found here
This field is optional.
": "{Integer}",SubModuleId
Required/mandatory field
Submodule identifier
Minimum value: 100000
": "{Integer}"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.
DutyId
Duty identifier
>{Integer}</DutyId>Name
Name of the duty
>{String}</Name>TranslatedName
Name translated to selected language. If no translation exists for the given langauage, english name will show.
>{String}</TranslatedName>Description
Description of the duty
>{String}</Description>TranslatedDescription
Description translated to selected language. If no translation exists for the given langauage, english description will show.
>{String}</TranslatedDescription>RequiredUserLevel
The user level required to have a duty. Only users having the same level or higher can have the duty. Therefore a duty can only be added to roles that have the same user level or higher.
User level (highest level first): Administrator, Partner, User, Portal user
Possible domain values can be found here
>{Integer}</RequiredUserLevel>AdmittanceLevel
How much the duty should weigh in regard to calculation of a users price category (for licence invoicing) . This field is accumulated for the duties a user is assigned, and the sum will define which price category the user should have.
Possible domain values can be found here
>{Integer}</AdmittanceLevel>CreatedAt
Date and time of creation
>{Datetime}</CreatedAt>SubModuleId
Submodule identifier
>{Integer}</SubModuleId>Name
Name of the sub-module
>ModuleId
Module identifier
>{Integer}</ModuleId>Name
Name of the module
>{String}</Name>ModuleLink
Module reference
>{String}</ModuleLink>SubModuleLink
Submodule reference
>{String}</SubModuleLink>Scope
Scope of the Duty
>{String}</Scope>IsChanged
Tells whether this object has been changed locally and are ready to be committed to the Repository
>{Boolean}</IsChanged>ChangedBy
EmployeeId of the employee making the change
>{Integer}</ChangedBy>IsPendingDeployment
Tells whether this object has been changed locally and is ready to be deployed from the Repository
>{Boolean}</IsPendingDeployment>DutyId
Duty identifier
": "{Integer}",Status
Status of the duty
Possible domain values can be found here
": "{Integer}",Name
Name of the duty
": "{String}",TranslatedName
Name translated to selected language. If no translation exists for the given langauage, english name will show.
": "{String}",Description
Description of the duty
": "{String}",TranslatedDescription
Description translated to selected language. If no translation exists for the given langauage, english description will show.
": "{String}",RequiredUserLevel
The user level required to have a duty. Only users having the same level or higher can have the duty. Therefore a duty can only be added to roles that have the same user level or higher.
User level (highest level first): Administrator, Partner, User, Portal user
Possible domain values can be found here
": "{Integer}",AdmittanceLevel
How much the duty should weigh in regard to calculation of a users price category (for licence invoicing) . This field is accumulated for the duties a user is assigned, and the sum will define which price category the user should have.
Possible domain values can be found here
": "{Integer}",CreatedAt
Date and time of creation
": "{Datetime}",SubModuleId
Submodule identifier
": "{Integer}",Name
Name of the sub-module
": {ModuleId
Module identifier
": "{Integer}",Name
Name of the module
": "{String}",ModuleLink
Module reference
": "{String}"SubModuleLink
Submodule reference
": "{String}",Scope
Scope of the Duty
": "{String}",IsChanged
Tells whether this object has been changed locally and are ready to be committed to the Repository
": "{Boolean}",ChangedBy
EmployeeId of the employee making the change
": "{Integer}",IsPendingDeployment
Tells whether this object has been changed locally and is ready to be deployed from the Repository
": "{Boolean}"
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 101015 HTTP 404 | Permission not found |
Error 101079 HTTP 400 | Mismatch in size of revision parameters |
Error 102949 HTTP 400 | Duty must have access points |
Error 101427 HTTP 400 | Module is required |
Error 101013 HTTP 404 | Sub-module not found |
Error 104416 HTTP 400 | User level is required |
Error 104417 HTTP 403 | You are not permitted to set this user level |
Error 107890 HTTP 400 | Permission "{0}" has higher required user level than duty. |