Jump to: navigation, search

Fetch single task by task ID

Method

GET

Syntax

GET /gtl/task/<solution_dbid>/<task_id>

Response Body

{
  "attribute_definitions":
  [
    {
      "name": "<attribute name>",
      "label": "<localized attribute label>",
      "type": "<string/date/int/img/list/age>",
      "category": "<core/ext/data>"
    },
    ...
  ],
  "task":
    {
      "core":
      {
        "<attribute_name>":
        {
           "value": <value>,
           "display_value": <display value>,
           "tooltip": <tooltip>,
           "missing": true
        },...
      },
      "ext":
      {
        ...
      },
      "data":
      {
        ...
      }
    }
 }
  • "data" attribute definitions are sorted ascending by the localized attribute label. "core" and "ext" attribute definitions are in the same order as they were in previous releases of iWD Manager.
  • "age" type has the following format:
"value":
  {
    "start": "<start_date_time>",
    "end": "<optional_end_date_time>"
  }
  • If "end" is present and not null, the UI should display the duration between "start" and "end". Otherwise, it should display the duration between "start" and the current time.
  • The process, department and capturePoint attributes contain names of business structure objects found by IDs (RTID) from the task: processId, departmentId and capturePointId, respectively. If an ID is set in a task but the corresponding object is missing, the attribute value is set to a default value (RTID) and a flag—missing: true—is set for such an attribute. The UI should display the default value in a specific way; for example crossed out and with a localized tooltip. Example: The attribute is missing.
  • "tooltip" and "display_value" are present only if different to the value. "display_value" is currently used only for channel.
  • HTTP 404 Not Found if the task was not found.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on December 19, 2017, at 03:03.