Table of Contents

Search

  1. Preface
  2. Introduction to Business Entity Services
  3. Enterprise Java Bean Business Entity Service Calls
  4. Representational State Transfer Business Entity Service Calls
  5. Simple Object Access Protocol Business Entity Service Calls
  6. Services for Cross-reference Records and BVT Calculations
  7. Supporting Corporate Linkage Service
  8. External Calls to Cleanse, Analyze, and Transform Data
  9. Using REST APIs to Add Records
  10. Using REST APIs to Upload Files

Request Body

Request Body

Send the task details in the request body. Use the Read Task API to get the details of the task.
The following table describes the task parameters in the request body:
Parameter
Description
taskType
A set of actions that you can perform on a record. Use the name attribute to specify the task type. For more information about task types, see the
Multidomain MDM Data Director Implementation Guide
.
taskId
ID of the task.
owner
User who performs the task.
title
Short description for the task.
comments
Comments for the task.
dueDate
Date when the owner must complete the task.
status
Status of the task in the workflow. Use one of the following two values:
  • Open: Task has not started or is in progress.
  • Closed: Task is completed or is cancelled.
priority
Level of importance of the task.
creator
User who creates the task.
createDate
Date when the task was created.
updatedBy
User who updates the task.
lastUpdateDate
Date when the task was last updated.
orsId
ID of the ORS as registered in the Databases tool in the Hub Console.
processId
ID of the workflow process that contains the task.
taskRecord
The root record or the cross-reference record associated with the task. Use the row ID or the source system and source key to specify the record.
businessEntity name
Name of the business entity to which the taskRecord belongs.
The following sample code uses the rowId to specify the taskRecord:
taskRecord: [{ businessEntity:{ name: 'Person', key:{ rowid: '233', systemName: '', sourceKey: '' } } }]

0 COMMENTS

We’d like to hear from you!