Delivering a Task

Delivering a task to its parent integration branch makes it active in any Application Object Manager (AOM) with that Workspace Context. For more information about Workspaces, see Using Siebel Tools.

To deliver a task

Modify the task in the Developer Workspace.
Test the updated task.
Deliver the task to its parent Integration Workspace.
1. Go to the Workspace Dashboard in your client application and open the Workspace that is being used for your task development.
2. Click Deliver on the Workspace Toolbar.

On delivering a task, the runtime definition of the task is created as an entry in the S_RR_TASK table.

During FullPublish, the S_RR_TASK table and related tables are reset to reflect the version of the task that remains in the MAIN Workspace.

Note: If there are different runtime definitions of the same task in the runtime table, modified in different Workspaces, then the appropriate definition will be picked up based on the Workspace Context defined in the AOM definition or selected by the user from the Workspace Dashboard at runtime.

About Deploying a Task

A deployed task is a task that is active. You create a task in your development environment, and then you deploy it to a testing or production environment.

As soon as you deliver a task to the Integration Workspace, it is compiled into the Runtime Repository and is active in that Workspace. If a migration is performed from that Workspace to any downstream Runtime Repository environment, then the task will also be active in that environment.

Inactivating a Deployed Task

The following procedure shows how to inactivate a deployed task.

To inactivate a deployed task

On the Task object in the Siebel Repository, set the Inactive Flag to TRUE.
Deliver the change to the parent Integration Workspace.

Any user who is leveraging that Workspace, whether in the Design Repository (DR) instance or in any downstream Runtime Repository (RR) environment migrated from that Integration Workspace, will ignore the inactive task.