This chapter covers the following topics:
You can add additional data in the JTF objects table. Metadata source objects have static definitions to dynamically retrieve data during runtime. This allows for the code to call the metadata source name, instead of writing the code out in every location.
Note: In some instances, Customer Profiles and Service Request notes, require a specific prefix or code name.
Perform the following steps to add data in JTF objects for use in Tasks Manager.
Responsibility: CRM Administrator
Steps
Navigate to Task and Escalation Manager > Setup > Objects Meta-data.
Enter a name, description, and unique object code.
Enter or select information in the fields for all sections that are needed for this source.
Seeded check box: It indicates that the data is seeded. It cannot be updated by users.
From task check box: Select this check box if tasks can be created, updated, and deleted using the standalone Task Manager. Otherwise, tasks can only be queried in read-only format.
Start Date: Enter a start date that the object code is available in the text field.
End Date: Enter an end date that the object code is unavailable in the text field.
Application: Select the Application name from the list of values.
Enter the following information in the Launch Details tab:
Function Name: Select the form function name registered as type, FORM from the LOV.
Parameter: Enter the parameters to be passed to the form function to open the source form. The following parameters are passed to open the source form.
ID - Source_object_id
NAME - Source_object_name
The rest of the parameters should be hard coded.
Launch Method: Use the drop-down list to select the Launch method. The Launch method is only for forms. They are:
FND_FUNCTION: Executes a specified form function only if the form is attached. It always starts a new instance of the form.
APP_NAVIGATE: Executes a specified form function only if the form is attached and also allows a form to be restarted if it is invoked a second time.
URL: Enter the URL for the application.
Web Function: Select the web function from the LOV. This is the JSP Function Name. It should be registered in Functions as type JSP.
Web Parameters: Enter the web parameters in the text field. These are the parameters to be passed to the JSP page. The following parameters are passed to open the source form.
ID - Source_object_id
NAME - Source_object_name
The rest of the parameters should be hard coded.
Enter the following database information in the Select Statement Details tab:
ID Column: Enter the ID value to be fetched from a given table in the text field, such as task_id. The ID identifies the unique column that is stored as the records place holder.
Name Column: Enter the NAME value to be fetched from a given table in the text field, such as task_number. This column shows as the main search/result column value a user uses to select data.
Details Column: Enter the details value to be fetched from given a table, such as description. The details column gives user more information on the column to choose from in the LOV listing.
Enter your select statement:
From: Enter the name of the table where the data is obtained, such as jtf_tasks_vl.
Where: Enter any Conditions of the selected data in the where clause, such as source_object_type_code = "TASK".
Order By: Enter the order by which the records should be sorted, such as task_number.
Select Statement: This read-only text field displays your select statement when clicking the Check Syntax button to validate the syntax of your statement before it is saved.
Enter the following information in the LOV and Data Security tab:
In the LOV region:
Window: Enter a title for the List of values window in the text field. This is the Title that appears for the LOV generated for this source object.
Name: Enter the column name for List of values specified in the Select Statement Detail's "Name Column" field.
Details: Enter the Title for details column for List of values specified in the Select Statement Detail's "Detail Columns" field.
In the Data Security Setup region:
Object Name: The name for a corresponding JTF_OBJECTS code. This name serves as the foreign key to FND_OBJECTS. This field is not required and can be empty (null).
Predicate Alias: This field adds security information to application query. It should only be used to avoid ambiguity when LOV query contains more than one table joined by data object primary key(s) values. For example, two tables ("jtf_tasks_b" and "jtf_tasks_tl") are used, then it must be entered with either "jtf_tasks_b" or "jtf_tasks_tl". Otherwise Oracle DBMS will report ambiguous task_id reference at the run time.
If it is entered and the object name is not null, the value will be passed to an internal API to add security to a generated query for the LOV. However, if the object name is empty, then security predicate will not be added to the generated query.
Refer to Customizing the List of Values (LOV) Security Access, Customizing Task Security chapter for details.
Define the object user in the Usage tab:
Object User: Select the object user from the list of values.
The Seeded check box is not editable. It indicates that the data is seeded.
Usage users are specified access locations where an object can be used. As long as the object is not seeded, all usages can be assigned.
When defining a new document, the Notes implementor or system administrators must associate Notes usage to the new document. In the Forms-based Notes, the document name appears in the Source list. Each item in the Source list has an associated related object, which appears in the Related To list.
Perform the following steps in Forms to define the source code usage as NOTES.
Steps
Navigate to Task and Escalation Manager > Setup > Objects Meta-data.
In the Tasks Setup: Object Types window opens, perform one of the following tasks:
If the source object code you want to seed already exists, then define the usage as NOTES.
If the source object code is not defined, then you must define the source object code, the name, and select its details and usage. (Usage should be NOTES.)
For detailed instruction on how to enter each field, please see Setting Up Metadata Objects.