This chapter covers the following topics:
Similar to the functionality of mapping task references to a source, implementors can use the Mapping Objects window to map both task assignee types and owner types to a source object for the Oracle Applications Framework based Task Manager.
In the Mapping Objects window, implementors or system administrators can select appropriate source objects from the list of values, and resource types used for both assignee and owner types from the "Used for Mapping Task owner" field. This limits the visibility of task assignee and owner types shown in the assignee and owner type list of values for a mapped source object. These resource types can be resources of any category including employee, group, team, party, partner, other, and to be hired.
After mapping task assignee and owner types to a source, end users will see only the mapped assignee and owner types displayed in the list of values. All other unmapped types will not be in the list. In addition, if none of the types is mapped to your source object, then end users will see all resource types from the owner and assignee list of values.
For example, if a task created for a service request can only be assigned to and owned by an individual resource or a resource group, then implementors should select a resource category of Group and Employee and map them to a source object, Service Request. Therefore, end users can select either Employee or Group from the drop-down list when assigning an owner or assignee to a task created for a service request.
To limit the functionality, implementors can put an end date to terminate the mapping or can select Applications to restrict the mapping usage to certain applications.
Be aware that implementors can also use the Mapping Objects window to Map Task and Notes Reference to a Source. When mapping assignee types to a source in the Mapping Objects window, Task Assignee is automatically displayed in the Map field located on the top of the window while References is displayed if it is for mapping references to a source.
Perform the following steps in Forms to define the mapping objects.
Steps
As the CRM Administrator, navigate to Task and Escalation Manager > Setup > Map Task Assignees to Source
In the Mapping Objects window, you can see the Resource Type populated in the Map field.
Select your source object from the LOV, for example, Sales Opportunity.
Select appropriate owner types in the Resource Type field that you want to appear in the drop-down list from the LOV. These selected owner types will also be used for assignee types.
Select an end date from the LOV.
Select the application where you want to extract your additional data from.
Save your information by clicking Save.
Repeat these steps for every object that you want to appear in the LOV for your source object.
In addition to the seeded date types (planned dates, scheduled dates and actual dates), you can use task date types to define other dates to track task progress, such as milestone and follow up dates. This functionality is used in the Forms-based Tasks only. The date types appear in the LOV on the Dates tab in the Task Details window in Tasks Forms.
You can limit the selection of the LOV shown in the Date Type field by mapping them to a source. For example, you can set the selection of date types from the LOV for a service request (source object) to be only Due Date and Follow Up Date.
Steps
As the CRM Administrator, navigate to Task and Escalation Manager > Setup > Define Task Date Types.
In the Task Date Types window, enter the task date type.
Enter a description for the task date type.
Enter a numeric value for the Sequence.
Define the Application field as the application that is seeding the data, for example, FND (Application Object Library). This field is not relevant to external customers.
If you want to limit the selection of the LOV shown in the Date Type field by mapping the task date types to a source, then perform the following steps:
In the Task Date Types window, click Map Date Types to open the Mapping Objects window.
Select the source object from the list of values (LOV).
Select the task date type from the LOV.
Optionally, set the end date for the task date type.
Define the application field as the application that is seeding the data, for example, FND (Application Object Library). This field is not relevant to external customers.
The Seeded check box is not editable.
Click Save.
The Task Mass Reassignment window used to mass reassign tasks to different resources is Declarative Page Flows (DPF)-enabled. It can link several pages together to represent a business flow. The Task Mass Reassignment window needs to be registered in business flows.
For how to register the screen in business flows, see Oracle E-Business Suite CRM System Administrator's Guide.