Developing the Task

This task is a step in Task Development Example.

This task includes creating and defining the task, including task properties, steps, connectors, and so on using the Task Editor. To begin with, the application developer creates the task, then refines the task, and then sets up access control.

Creating the Task

After the team reaches consensus on the task view layouts for the task, the application developer does the following to create the task:

1. Makes required additions and modifications in the configuration for the business logic.

   This configuration might include the business object, business component, links, picklists, and so on.

2. Creates or reuses the required applets.

3. Creates or reuses the required task views.

Next, the application developer refines the task.

Refining the Task

The application developer does the following to refine the task:

1. Add links to the new task views.

2. Adds an insert Operation step before the first view in the submission task.

3. Adds an update Operation step after the task view step in the review task.

4. Reviews and updates properties and multivalue properties for task steps.

5. Makes sure that the task contains no validation errors or warnings, including setting the Instance ID task property that the business analyst identified.

6. Creates a relationship between the submission task and the Common Tasks task group.

Next, the application developer sets up access control.

Setting Up Access Control

The application developer does the following to set up access control:

• Makes sure the responsibility for the test user possesses the visibility to run the submission task. For more information, see Adding a Responsibility to a Task.

• Makes sure the Siebel client displays the customizations.