Oracle Migration Tool On Demand Guide > Migrating Workflow Rules and Action Sets > Elements and Sections in the Workflow Action Sets Output File >

Create Task Workflow Action Set


Table 60 describes the elements and sections in the Create Task workflow action set XML output file.

Table 60. Elements and Sections in the Create Task Workflow Action Set XML File
Element or Section
Description

<data:WorkflowName>Opportunity Approval
</data:WorkflowName>

<WorkflowName> contains the name of the workflow rule with which this action is associated. When performing an Upsert or InsertOrUpdate operation for workflow actions, this name is used to find a matching workflow rule.

<data:WorkflowAction>
. . .
</data:WorkflowAction>

The <WorkflowAction> section contains the details of the workflow action.

<data:WorkflowAction>
  <data:Name>CreateTaskTest</data:Name>
. . .
</data:WorkflowAction>

<Name> is the name of the workflow action.

<data:WorkflowAction>
. . .
  <data:Active>false</data:Active>
. . .
</data:WorkflowAction>

<Active> specifies whether the workflow action is active (true) or is inactive (false).

<data:WorkflowAction>
. . .
  <data:Order>3</data:Order>
. . .
</data:WorkflowAction>

<Order> is the order number for the workflow action within the set of actions on the workflow rule. It determines the order in which Oracle CRM On Demand invokes the sequence of workflow actions on the workflow rule.

<data:WorkflowAction>
. . .
  <data:WorkflowCreateTaskAction>
. . .
  </data:WorkflowCreateTaskAction>
</data:WorkflowAction>

The <WorkflowCreateTaskAction> section contains the details of the Create Task workflow action.

<data:WorkflowAction>
. . .
  <data:WorkflowCreateTaskAction>
    <data:Owner>O_Primary Owner Id</data:Owner>
. . .
  </data:WorkflowCreateTaskAction>
</data:WorkflowAction>

<Owner> specifies the owner for the task. The <Owner> element's value depends on the <OwnerType> element, as follows:

  • If <OwnerType> is set to U (Specific User), then the <Owner> element contains the name of the user.
  • If the <OwnerType> element is set to R (Relative User On Record), then the value of the <Owner> element is defined, see Table 61.

<data:WorkflowAction>
. . .
  <data:WorkflowCreateTaskAction>
. . .
    <data:OwnerType>R</data:OwnerType>
. . .
  </data:WorkflowCreateTaskAction>
</data:WorkflowAction>

<OwnerType> corresponds to the Owner field in the user interface. The valid values are:

  • R. Corresponds to the Relative User On Record option in the user interface.
  • U. Corresponds to the Specific User option in the user interface.

<data:WorkflowAction>
. . .
  <data:WorkflowCreateTaskAction>
. . .
    <data:Type>Approval</data:Type>
. . .
  </data:WorkflowCreateTaskAction>
</data:WorkflowAction>

<Type> is the activity type.

<data:WorkflowAction>
. . .
  <data:WorkflowCreateTaskAction>
. . .
    <data:SubType>Callback</data:SubType>
. . .
  </data:WorkflowCreateTaskAction>
</data:WorkflowAction>

<SubType> is the activity subtype.

<data:WorkflowAction>
. . .
  <data:WorkflowCreateTaskAction>
. . .
    <data:DueDate>Today()+2</data:DueDate>
. . .
  </data:WorkflowCreateTaskAction>
</data:WorkflowAction>

<DueDate> contains an expression that evaluates to the due date for the task.

<data:WorkflowAction>
. . .
  <data:WorkflowCreateTaskAction>
. . .
    <data:Priority>2-Medium</data:Priority>
. . .
  </data:WorkflowCreateTaskAction>
</data:WorkflowAction>

<Priority> specifies the priority of the task.

<data:WorkflowAction>
. . .
  <data:WorkflowCreateTaskAction>
. . .
    <data:Status>Not Started</data:Status>
. . .
  </data:WorkflowCreateTaskAction>
</data:WorkflowAction>

<Status> specifies the status of the task.

<data:WorkflowAction>
. . .
  <data:WorkflowCreateTaskAction>
. . .
    <data:TaskCurrency>CAD</data:TaskCurrency>
. . .
  </data:WorkflowCreateTaskAction>
</data:WorkflowAction>

<TaskCurrency> contains the three-character currency code for the task.

<data:WorkflowAction>
. . .
  <data:WorkflowCreateTaskAction>
. . .
    <data:Private>false</data:Private>
. . .
  </data:WorkflowCreateTaskAction>
</data:WorkflowAction>

<Private> specifies whether the task is visible only to the task user (true), or is visible to users other than the task user (false).

<data:WorkflowAction>
. . .
  <data:WorkflowCreateTaskAction>
. . .
    </data:Subject>
. . .
  </data:WorkflowCreateTaskAction>
</data:WorkflowAction>

<Subject> contains the subject line for the task.

<data:WorkflowAction>
. . .
  <data:WorkflowCreateTaskAction>
. . .
    <data:Description></data:Description>
  </data:WorkflowCreateTaskAction>
</data:WorkflowAction>

<Description> contains the description of the task.

System Names and Display Names for Owner and To Element Values for Relative User on Record

Table 61 shows the system names and corresponding display names for the values that can appear in the following elements:

  • The <Owner> element in the Create Task workflow action set XML file, when the <OwnerType> element is set to R (Relative User on Record).
  • The <To> element in the Send Email workflow action set XML file, when the <ToType> element is set to R (Relative User on Record).

NOTE:  The T_Team Role values are available for the Account, Contact, Lead, Opportunity, and Service Request record types only.

Table 61. System Names and Display Names for the Owner and To Element Values for Relative User On Record
System Name in the XML File
Display Name

C_

Service Request Created By

MA_Account Id

Account Owner's Manager

M_Owned By Id

Object Owner's Manager

M_Owner Id

Lead Owner's Manager

M_Primary HH Owner Id

Household Owner's Manager

M_Primary Owner Id

Object Owner's Manager

M_Sales Rep Id

Salesperson's Manager

OA_Account Id

Account Owner

O_Owned By Id

Service Request Owner

O_Owner Id

Lead Owner

O_Primary HH Owner Id

Household Owner

O_Primary Owner Id

Object Owner

O_Sales Rep Id

Salesperson

T_Team Role_Consultant

Object Team - Consultant

T_Team Role_Executive Sponsor

Object Team - Executive Sponsor

T_Team Role_Other

Object Team - Other

T_Team Role_Owner

Object Team - Owner

T_Team Role_Partner

Object Team - Partner

NOTE:  For the Account, Contact, Lead, Opportunity, and Service Request record types, any custom roles that are added to the record type can be used in the Relative User on Record element, in addition to the values shown in Table 61. The system name for a custom team role is in the format T_Team Role_teamrolename, where teamrolename is the name given to the team role.

Oracle Migration Tool On Demand Guide, Release 35 Copyright © 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices.