API

Production APIs

GET production/task-triggers/{productionTaskTriggerId}

Details of production task trigger

HTTP method GET
URI https://api.rambase.net/production/task-triggers/{productionTaskTriggerId}
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {productionTaskTriggerId} Production task trigger id
Integer, minimum 100000
Successful HTTP status code 200
API resource identifier 5508, version 10

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.

$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]
$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.

Format:
1
<ProductionTaskTrigger>
2
     <ProductionTaskTriggerId
ProductionTaskTriggerId

Production task trigger id

>
{Integer}</ProductionTaskTriggerId>
3
     <Status
Status

Status of the production task trigger

Possible domain values can be found here

>
{Integer}</Status>
4
     <Name
Name

Name of the production task trigger

>
{String}</Name>
5
     <Description
Description

Description of the production task trigger

>
{String}</Description>
6
     <Location>
7
          <LocationId
LocationId

Location identifier

>
{Integer}</LocationId>
8
          <ShortName
ShortName

Unique abbreviation/short name of the location

>
{String}</ShortName>
9
          <LocationLink
LocationLink

Location reference

>
{String}</LocationLink>
10
     </Location>
11
     <TaskProcessTemplate
TaskProcessTemplate

Task process template the tasks should be created from

>
12
          <TaskProcessTemplateId
TaskProcessTemplateId

Unique identifier for task process template

>
{Integer}</TaskProcessTemplateId>
13
          <Name
Name

Name of the task process template

>
{String}</Name>
14
          <TaskProcessTemplateLink
TaskProcessTemplateLink

Task process template reference

>
{String}</TaskProcessTemplateLink>
15
     </TaskProcessTemplate>
16
     <RetriggerSettings>
17
          <Level
Level

Degree of details. State if the task should be triggered based on only product id or in addition one or more varaiables.

Possible domain values can be found here

>
{Integer}</Level>
18
          <IntervalDays
IntervalDays

Number of days since last production before the task process will be re triggered based on the degree of details.
If never triggerd before it will do it the first time production runs.

>
{Integer}</IntervalDays>
19
          <CheckQualityIssues
CheckQualityIssues

Check for quality issues. If quality issue since last time trigger, re trigger

>
{Boolean}</CheckQualityIssues>
20
     </RetriggerSettings>
21
</ProductionTaskTrigger>
1
{
2
     "productionTaskTrigger": {
3
          "productionTaskTriggerId
ProductionTaskTriggerId

Production task trigger id

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

Status of the production task trigger

Possible domain values can be found here

":
"{Integer}",
5
          "name
Name

Name of the production task trigger

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

Description of the production task trigger

":
"{String}",
7
          "location": {
8
               "locationId
LocationId

Location identifier

":
"{Integer}",
9
               "shortName
ShortName

Unique abbreviation/short name of the location

":
"{String}",
10
               "locationLink
LocationLink

Location reference

":
"{String}"
11
          },
12
          "taskProcessTemplate
TaskProcessTemplate

Task process template the tasks should be created from

":
{
13
               "taskProcessTemplateId
TaskProcessTemplateId

Unique identifier for task process template

":
"{Integer}",
14
               "name
Name

Name of the task process template

":
"{String}",
15
               "taskProcessTemplateLink
TaskProcessTemplateLink

Task process template reference

":
"{String}"
16
          },
17
          "retriggerSettings": {
18
               "level
Level

Degree of details. State if the task should be triggered based on only product id or in addition one or more varaiables.

Possible domain values can be found here

":
"{Integer}",
19
               "intervalDays
IntervalDays

Number of days since last production before the task process will be re triggered based on the degree of details.
If never triggerd before it will do it the first time production runs.

":
"{Integer}",
20
               "checkQualityIssues
CheckQualityIssues

Check for quality issues. If quality issue since last time trigger, re trigger

":
"{Boolean}"
21
          }
22
     }
23
}

Possible error codes the response might return:

Error 101606 HTTP 404 Module not found