addTaskRoleAssociation
- Description
- This transaction creates additional task owner role associations for an existing task definition.
- Web Services
- Operation name: addTaskRoleAssociation
- Example
- In addition to brand managers and assistant brand managers, grant
marketing managers access to tasks that involve campaigns.
Enable a superuser role to access and perform all enrichment tasks.
- Usage information
- At least one task role association is created for each task definition.
This is a fine-grained transaction that adds an extra task owner role to an existing task definition.
- Preconditions
- A task definition must exist.
A user role must exist.
- Mandatory input
- TaskDefinitionId
- TaskOwnerRole
- Inquiry levels
- Not applicable
- Filter values
- Not applicable
- Transaction behavior
- A single task definition can have multiple task role associations.
Using the addTaskDefinition transaction, you can create multiple task role associations while creating a new task definition. However, the addTaskRoleAssociation transaction can only add one task owner role at a time.
A task role association is part of the attributes of a task instance. It represents the task definition that applies to the given task instance and the task owner role allowed to perform the task instance. Each task instance can only have one task role association at any given time, although the task definition may have multiple task role associations.
If the StartDate is not provided, the current system date is used by default.
The EndDate must be equal to or later than the StartDate.
- Request message
- <DWLTxType> addTaskRoleAssociation
<DWLTxObject> TaskRoleAssocBObj
<DWLObject> TaskRoleAssocBObj
- Response objects
- TaskRoleAssocBObj
- Special note
- Not applicable