API

Quality management APIs

GET quality/risks/{riskId}/potential-consequences/{potentialConsequenceId}/score-log/{scoreLogEntryId}

Gets a risk score log entry

HTTP method GET
URI https://api.rambase.net/quality/risks/{riskId}/potential-consequences/{potentialConsequenceId}/score-log/{scoreLogEntryId}
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {riskId} Identifier of the risk
Integer, minimum 100000
- URI parameter {potentialConsequenceId} Potential consequence identifier
Integer, minimum 1
- URI parameter {scoreLogEntryId} Score log entry identifier
Integer, minimum 1
Successful HTTP status code 200
API resource identifier 5220, version 8

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.

$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
<ScoreLogEntry>
2
     <ScoreLogEntryId
ScoreLogEntryId

Score log entry identifier

>{Integer}</ScoreLogEntryId>
3
     <AddedAt
AddedAt

Date and time this score log was added

>{Datetime}</AddedAt>
4
     <Comment
Comment

Comment to the score log entry

>{String}</Comment>
5
     <Score
Score

Risk score in score log

>{Integer}</Score>
6
     <Severity>
7
          <Rating
Rating

Severity rating of a potential consequence

>{Integer}</Rating>
8
     </Severity>
9
     <Likelihood>
10
          <Level
Level

Likelihood level of a potential consequence

>{Integer}</Level>
11
     </Likelihood>
12
     <AddedBy
AddedBy

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

>
13
          <UserId
UserId

User identifier

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

>{Integer}</UserId>
14
          <FirstName
FirstName

First name of the user

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

>{String}</FirstName>
15
          <Name
Name

Name of the user

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

>{String}</Name>
16
          <UserLink
UserLink

User reference

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

>{String}</UserLink>
17
     </AddedBy>
18
</ScoreLogEntry>
1
{
2
     "scoreLogEntry": {
3
          "scoreLogEntryId
ScoreLogEntryId

Score log entry identifier

": "{Integer}",
4
          "addedAt
AddedAt

Date and time this score log was added

": "{Datetime}",
5
          "comment
Comment

Comment to the score log entry

": "{String}",
6
          "score
Score

Risk score in score log

": "{Integer}",
7
          "severity": {
8
               "rating
Rating

Severity rating of a potential consequence

": "{Integer}"
9
          },
10
          "likelihood": {
11
               "level
Level

Likelihood level of a potential consequence

": "{Integer}"
12
          },
13
          "addedBy
AddedBy

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

": {
14
               "userId
UserId

User identifier

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

": "{Integer}",
15
               "firstName
FirstName

First name of the user

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

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

Name of the user

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

": "{String}",
17
               "userLink
UserLink

User reference

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

": "{String}"
18
          }
19
     }
20
}

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 107194 HTTP 400 Score log entry not found
Error 107191 HTTP 404 Potential consequence not found