Quality management APIs
Add new related QHSES issue
HTTP method | POST |
URI | https://api.rambase.net/quality/risks/{riskId}/related-issues |
Supported formats | Xml, Html, Json (ex. $format=json) |
- URI parameter {riskId} |
Identifier of the risk
Integer, minimum 100000 |
Successful HTTP status code | 201 |
API resource identifier | 5340, version 2 |
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.
QualityIssueId
Required/mandatory field
Quality issue identifier
Minimum value: 100000
>{Integer}</QualityIssueId>QualityIssueId
Required/mandatory field
Quality issue 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.
RelatedIssueId
Identifier of the relation with related issues
>{Integer}</RelatedIssueId>AddedAt
Date and time when relation was added
>{Datetime}</AddedAt>QualityIssueId
Quality issue identifier
>{Integer}</QualityIssueId>Status
Status of quality issue. 1: Registering, 2: Analyzing, 4: Pending actions, 8: Reviewing, 9: Closed
Possible domain values can be found here
>{Integer}</Status>Description
Description of quality issue
>{String}</Description>Type
Quality issue type. I.E "Incident", "Observation" or "Improvement proposal"
Possible domain values can be found here
>{Integer}</Type>Title
Title of the issue
>{String}</Title>Category
Category of the quality issue. Together with type this should apply information on which field/area of a system the quality issue is addressing
Possible domain values can be found here
>{Integer}</Category>DueDate
Time and date when this issue should be resolved
>EmployeeId
Employee identifier
>{Integer}</EmployeeId>LastName
Last name of employee
>{String}</LastName>FirstName
First name of employee
>{String}</FirstName>EmployeeLink
Employee reference
>{String}</EmployeeLink>EmployeeId
Employee identifier
>{Integer}</EmployeeId>LastName
Last name of employee
>{String}</LastName>FirstName
First name of employee
>{String}</FirstName>EmployeeLink
Employee reference
>{String}</EmployeeLink>QualityIssueLink
API reference to the object
>{String}</QualityIssueLink>RelatedIssueLink
API reference to the item
>{String}</RelatedIssueLink>RelatedIssueId
Identifier of the relation with related issues
": "{Integer}",AddedAt
Date and time when relation was added
": "{Datetime}",QualityIssueId
Quality issue identifier
": "{Integer}",Status
Status of quality issue. 1: Registering, 2: Analyzing, 4: Pending actions, 8: Reviewing, 9: Closed
Possible domain values can be found here
": "{Integer}",Description
Description of quality issue
": "{String}",Type
Quality issue type. I.E "Incident", "Observation" or "Improvement proposal"
Possible domain values can be found here
": "{Integer}",Title
Title of the issue
": "{String}",Category
Category of the quality issue. Together with type this should apply information on which field/area of a system the quality issue is addressing
Possible domain values can be found here
": "{Integer}",DueDate
Time and date when this issue should be resolved
": {EmployeeId
Employee identifier
": "{Integer}",LastName
Last name of employee
": "{String}",FirstName
First name of employee
": "{String}",EmployeeLink
Employee reference
": "{String}",EmployeeId
Employee identifier
": "{Integer}",LastName
Last name of employee
": "{String}",FirstName
First name of employee
": "{String}",EmployeeLink
Employee reference
": "{String}"QualityIssueLink
API reference to the object
": "{String}"RelatedIssueLink
API reference to the item
": "{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 105778 HTTP 404 | Issue not found. |
Error 107959 HTTP 400 | You have only admittance to issues connected to your account |