|
Siebel Business Process Framework: Task UI Guide > Deploying Tasks >
Deploying Tasks from Siebel Tools
Deploying a task requires two steps: publishing and activating. The task definitions (stored as repository objects) must be published to the run-time environment, and then they must be activated in the run-time environment. The process for deploying a task involves the following procedures:
- Publish the task from Siebel Tools.
This makes the task visible in the run-time client application. For more information, see Publishing Tasks.
- Activate the task from the run-time client.
This makes the task available to users. For more information, see Activating Tasks.
Then, after you publish and activate the task, you can assign responsibilities for running the task and the access rights they have on the inbox. For more information, see Controlling Task Access Privileges. Publishing Tasks
Because the task definitions are stored in the repository, you must compile the repository before publishing when you have added repository objects (such as business components, business services, and views) to the task. NOTE: When you publish tasks that contain subtasks, make sure to publish the subtasks prior to publishing the main task so that the subtasks are available to the main task in the run-time environment.
When you publish a task, the task definition is read from the repository and written to the run-time environment (with its deployment parameters) in XML format. The task's deployment parameters (Replication, Activation Date, Expiration Date) are used when activating the task. To publish a task from Siebel Tools
- In the Object Explorer (in Siebel Tools), click the Task object type.
- In the Tasks OBLE, select the task you want to publish.
- On the WF/Task Editor toolbar, click the Publish button.
NOTE: If the WF/Task Editor toolbar is not currently displayed, choose Toolbars > WF/Task Editor Toolbar from the View menu.
When you click Publish, you are prompted to either validate before you publish or to go ahead.
- Click Yes to go ahead and publish the task.
When the status changes from In Progress to Completed, the task becomes visible in run-time client application.
After the task has been published, it must be activated before it can be used in the run-time environment. NOTE: If you use the Publish/Activate button (rather than the Publish button) to publish the task, there is no need to activate the task separately in the run-time application.
Activating Tasks
After the task has been published, it must be activated before it can be used in the run-time environment. You specify the deployment status of the published task definitions using the Repository Task Deployment view in the run-time client. This view consists of the following two applets:
- Published Tasks List Applet. Displays the completed tasks from the repository tables.
NOTE: When a task is revised and published, the repository version of this task is incremented. When you click on the task name link, the applet displays the child items (published task definitions) of the task.
- Task Deployment Repository List Applet. Displays the tasks that have been deployed.
In the run-time environment, the deployment status of a deployed task can be Active, Outdated, or Inactive:
- A task that is active is the basis for new tasks that are created. New instances of the task are created using this definition. At any given time, there can only be one active version of a task with a particular name.
- A task that is outdated allows tasks that are already actively in progress or in the inbox to continue using the prior definition, but new task instances are not based on this definition. When a task definition is outdated, no new instance can be created based on that definition, but existing tasks continue using that version.
- If a task is inactive, then no new or paused instances can continue using this definition.
To activate a task in the run-time environment
- Launch the run-time client, and log in.
- From the application-level menu in the run-time client, choose Navigate > Site Map > Administration - Business Process > Task Deployment.
This displays the Task Deployment view where you can activate the task.
- Query for the task you just published.
- Select the task, and then click Activate.
The syntax is checked for validity, and the deployment status of the task changes to Active.
NOTE: When you activate a task, the deployment status of the previous active version (if any) changes to Outdated.
- Specify the deployment parameters for the task in the Task Deployment Repository List Applet:
- Set the activation date in the Activation Date/Time field.
- Set the expiration date in the Expiration Date/Time field.
- Set the replication to None, unless you are deploying the Task to mobile clients.
NOTE: If you are deploying the Task to mobile clients, see Setting Up Tasks for Running on Mobile Clients.
After you have activated the task, you must now assign the responsibilities for running the task and the access rights they have on the inbox. For more information, see Controlling Task Access Privileges. To deactivate a task in the run-time environment
- Launch the run-time client, and log in.
- From the application-level menu in the run-time client, choose Navigate > Site Map > Administration - Business Process > Task Deployment.
This displays the Task Deployment view,
- Query for the active or outdated task definition you want to deactivate (in the lower applet for Active Tasks).
- Select the task, and then click Deactivate Task.
The deployment status of this task changes to Inactive.
To delete a task in the run-time environment
- Launch the run-time client, and log in.
- From the application-level menu in the run-time client, choose Navigate > Site Map > Administration - Business Process > Task Deployment.
This displays the Task Deployment view,
- Query for the active, inactive, or outdated task definition you want to delete (in the lower applet for Active Tasks).
- Click to select the task, and then click Delete Task.
CAUTION: Deleting a deployed definition impacts all running instances of that definition and might corrupt the data. It is recommended that you do not delete a deployed task definition unless the task definition has been deactivated.
|
