API

Quality management APIs

POST quality/issues/{qualityIssueId}/actions

Creates a new action to the quality issue.

HTTP method POST
URI https://api.rambase.net/quality/issues/{qualityIssueId}/actions
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {qualityIssueId} Quality issue identifier
Integer, minimum 100000
Successful HTTP status code 201
API resource identifier 4556, 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.

Format:
1
<QualityIssueAction>
2
     <Type
Type

Required/mandatory field

Type of an action. Immediate, corrective or suggested

Applicable domain values can be found here

>
{String}</Type>
3
     <Task>
4
          <TaskId
TaskId

Required/mandatory field

Unique task identifier

Minimum value: 100000

>
{Integer}</TaskId>
5
     </Task>
6
     <QualityCause
QualityCause

This field is optional.

>
7
          <QualityCauseId
QualityCauseId

Reference to the cause of the action.

Minimum value: 1

This field is optional.

>
{Integer}</QualityCauseId>
8
     </QualityCause>
9
</QualityIssueAction>
1
{
2
     "qualityIssueAction": {
3
          "type
Type

Required/mandatory field

Type of an action. Immediate, corrective or suggested

Applicable domain values can be found here

":
"{String}",
4
          "task": {
5
               "taskId
TaskId

Required/mandatory field

Unique task identifier

Minimum value: 100000

":
"{Integer}"
6
          },
7
          "qualityCause
QualityCause

This field is optional.

":
{
8
               "qualityCauseId
QualityCauseId

Reference to the cause of the action.

Minimum value: 1

This field is optional.

":
"{Integer}"
9
          }
10
     }
11
}

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.

Format:
1
<QualityIssueAction>
2
     <QualityIssueActionId
QualityIssueActionId

Action identifier

>
{Integer}</QualityIssueActionId>
3
     <Type
Type

Type of an action. Immediate, corrective or suggested

Possible domain values can be found here

>
{String}</Type>
4
     <AddedAt
AddedAt

Time and date when this action was added

>
{Datetime}</AddedAt>
5
     <AddedBy>
6
          <UserId
UserId

User identifier

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

First name of the user

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

Name of the user

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

User reference

>
{String}</UserLink>
10
     </AddedBy>
11
     <Task>
12
          <TaskId
TaskId

Unique task identifier

>
{Integer}</TaskId>
13
          <Status
Status

The status of a task

Possible domain values can be found here

>
{Integer}</Status>
14
          <Title
Title

The title/summary of the task

>
{String}</Title>
15
          <Description
Description

The description of the task

>
{String}</Description>
16
          <DeadlineAt
DeadlineAt

Date and time of when this task must be completed.

>
{Datetime}</DeadlineAt>
17
          <CompletedAt
CompletedAt

The full date and time when a task was completed

>
{Datetime}</CompletedAt>
18
          <Activity
Activity

Task type: Email, Phone call, Followup

Possible domain values can be found here

>
{Integer}</Activity>
19
          <AssignedTo
AssignedTo

The userId of the person this task is assigned to (responsible for doing the work)

>
20
               <EmployeeId
EmployeeId

Employee identifier

>
{Integer}</EmployeeId>
21
               <LastName
LastName

Last name of employee

>
{String}</LastName>
22
               <FirstName
FirstName

First name of employee

>
{String}</FirstName>
23
               <EmployeeLink
EmployeeLink

Employee reference

>
{String}</EmployeeLink>
24
          </AssignedTo>
25
          <TaskLink
TaskLink

Task reference

>
{String}</TaskLink>
26
     </Task>
27
     <QualityCause>
28
          <QualityCauseId
QualityCauseId

Reference to the cause of the action.

>
{Integer}</QualityCauseId>
29
          <QualityCauseLink
QualityCauseLink

Document reference of a cause

>
{String}</QualityCauseLink>
30
     </QualityCause>
31
</QualityIssueAction>
1
{
2
     "qualityIssueAction": {
3
          "qualityIssueActionId
QualityIssueActionId

Action identifier

":
"{Integer}",
4
          "type
Type

Type of an action. Immediate, corrective or suggested

Possible domain values can be found here

":
"{String}",
5
          "addedAt
AddedAt

Time and date when this action was added

":
"{Datetime}",
6
          "addedBy": {
7
               "userId
UserId

User identifier

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

First name of the user

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

Name of the user

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

User reference

":
"{String}"
11
          },
12
          "task": {
13
               "taskId
TaskId

Unique task identifier

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

The status of a task

Possible domain values can be found here

":
"{Integer}",
15
               "title
Title

The title/summary of the task

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

The description of the task

":
"{String}",
17
               "deadlineAt
DeadlineAt

Date and time of when this task must be completed.

":
"{Datetime}",
18
               "completedAt
CompletedAt

The full date and time when a task was completed

":
"{Datetime}",
19
               "activity
Activity

Task type: Email, Phone call, Followup

Possible domain values can be found here

":
"{Integer}",
20
               "assignedTo
AssignedTo

The userId of the person this task is assigned to (responsible for doing the work)

":
{
21
                    "employeeId
EmployeeId

Employee identifier

":
"{Integer}",
22
                    "lastName
LastName

Last name of employee

":
"{String}",
23
                    "firstName
FirstName

First name of employee

":
"{String}",
24
                    "employeeLink
EmployeeLink

Employee reference

":
"{String}"
25
               },
26
               "taskLink
TaskLink

Task reference

":
"{String}"
27
          },
28
          "qualityCause": {
29
               "qualityCauseId
QualityCauseId

Reference to the cause of the action.

":
"{Integer}",
30
               "qualityCauseLink
QualityCauseLink

Document reference of a cause

":
"{String}"
31
          }
32
     }
33
}

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 101420 HTTP 404 Setting definition not found