Create Tasks

You can configure object workflows to trigger auto-creation and assignment of tasks.

You can define tasks action for only those objects that support the creation of tasks. For other objects, the tasks option is disabled.

Here's how you can create a task:

1. Navigate to Application Composer.

2. From the Overview page, click Object Workflows.

3. Click Create.

4. Select an Object and provide a meaningful Name and Description.

5. Define the trigger condition using When a record is created or When a record is updated event point.

6. Under the Actions region, click Create for Tasks Creation.

   This opens the Create Action: Tasks Creation page.

7. Provide the Name and Description for the event action and optionally set the Execution Schedule.

8. Use the Task Details region to configure a task based on your requirements. Here's how you can use the tasks details region:

   • Select a Subject and Description, as appropriate, for your task notification.

   • Select the Due Date and Start Date for a task. When you select a date, you can also provide logical conditions for these dates, for example, a Due Date must be 30 days after the Start Date.

   • Select an Owner for the task. The values in this list change depending on the object for which the task is being defined. A task can have only one owner: either an individual person or a single resource. You can search for users by name or user ID. You can store a user's PartyID or GUID in a text field you create and use the value as the task owner.

   • Select the Resources for the task. The values in these lists change depending on the object for which the task is being defined. Resources can be owner, resource team, resource team with different access levels, member functions, and so on. You can store multiple comma-separated PartyIDs or GUIDs in a text field you create and use the values as task resources.

     For example, when an opportunity reaches a Close Date and the status is Open, you can use the task creation action to assign a follow up task to the owner of the opportunity.

   • Select a Primary Contact for the task. You can select one from contacts related to the object record, or specify one by name. If the selected object contains user-defined text fields that store the contact's name or contactID, you can select those fields to be set as primary contact.

   • Select the Type to which a task belongs. This field uses FND lookup for values. The delivered values are call, chat, demo, e-mail, and meeting.

   • Assign a Priority to the task. The default priority is Medium.

9. If a standard object or an object you created has more than one one-to-many relationships defined through dynamic choice list or reference relationship with the Activity you have chosen, the Related To field appears at the bottom. This Related To field shows the first created relationship as default.

   You can select this field only once for the object in context, after which the field appears as read only.

10. Save the event action.

Note: If an object for which you're defining this event action contains a customer, that customer is automatically included in the created task.

For an example of how you configure tasks, see Configuring Object Workflows: Worked Example topic.

Creating Tasks Using Child Objects

When you configure an object workflow using a child object, the fields that you select are specific only to that child object.

When a child-object based task is triggered, the task is assigned to the parent object of that child. You can't configure a task for a child object of another child object.

Creating Tasks Using Objects with No Associated Activity

You can create a task for a standard object or an object you created even if it doesn't have a relationship with an Activity. If you try to create a task on an object with no relationship to an Activity, you see a message letting you know that a standalone task will be created unless you first create such a relationship. After they're created, standalone activities will show in the task owner's Activity work area in the desktop UI, and in the top-level Activities card in the application UI.