Quality management APIs
Gets a suggested action.
| HTTP method | GET |
| URI | https://api.rambase.net/quality/issues/{qualityIssueId}/suggested-actions/{suggestedActionId} |
| Supported formats | Xml, Html, Json (ex. $format=json) |
| - URI parameter {qualityIssueId} |
Quality issue identifier
Integer, minimum 100000 |
| - URI parameter {suggestedActionId} |
Suggested action identifier.
Integer, minimum 1 |
| Successful HTTP status code | 200 |
| API resource identifier | 4661, version 3 |
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.
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.
| $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. |
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.
QualityIssueSuggestedActionId
Suggested action identifier.
>{Integer}</QualityIssueSuggestedActionId>Title
Title of a suggested action.
>{String}</Title>Description
Description of a suggested action.
>{String}</Description>AddedAt
Date and time when this suggested action was added.
>{Datetime}</AddedAt>IsRejected
Tells if suggested action was rejected
>{Boolean}</IsRejected>UserId
User identifier
>{Integer}</UserId>UserLink
User reference
>{String}</UserLink>Name
Name of the user
>{String}</Name>QualityIssueSuggestedActionId
Suggested action identifier.
": "{Integer}",Title
Title of a suggested action.
": "{String}",Description
Description of a suggested action.
": "{String}",AddedAt
Date and time when this suggested action was added.
": "{Datetime}",IsRejected
Tells if suggested action was rejected
": "{Boolean}",UserId
User identifier
": "{Integer}",UserLink
User reference
": "{String}",Name
Name of the user
": "{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 101566 HTTP 404 | User not found |
| Error 105861 HTTP 404 | Issue action not found |
| Error 106066 HTTP 400 | Action is not of type suggested action. |