Siebel Business Process Framework: Task UI Guide > Testing, Troubleshooting, Deploying, and Administering a Task UI > Deploying and Migrating a Task UI >

Process of Deploying a Task UI


This process is a step in Roadmap for Developing a Task UI.

To deploy a task UI, perform the following tasks:

  1. Preparing to Publish a Task UI
  2. Publishing a Task UI
  3. Activating a Task UI
  4. Adding a Responsibility to a Task UI

A deployed task is a task UI that is published and activated. You create a task UI in your development environment, and then you deploy it to a testing or production environment. You can use Siebel Tools to publish the task and then activate it in the Siebel client. This process deploys task objects from the SRF (Siebel Repository File) to the run-time environment.

As an alternative, you can publish and activate a task UI in Siebel Tools. For more information, see Publishing and Activating a Task UI in Siebel Tools.

Preparing to Publish a Task UI

You must compile the SRF before you publish a task UI. If you add or modify repository objects that are part of the task UI or that this task references, then you must compile the SRF. Example objects in the SRF that the task might require include business components, business services, and views.

To prepare to publish a task UI

  1. Validate the task UI.

    For more information, see Validating a Task UI.

  2. Compile modified objects:
    1. In Siebel Tools, choose the Tools menu, and then the Compile Projects menu item.
    2. In the Object Compiler dialog box, click Locked Projects, and then click Compile.

Publishing a Task UI

Publishing a task UI makes the task visible in the Siebel client. Siebel CRM reads the object definition of the task UI from the SRF when you publish it, and then writes the definition and deployment parameters in XML format to the run-time environment. If your task UI includes a subtask step, then you must publish the subtask first so that the subtask is available to the parent task UI in the run-time environment.

To publish a task UI

  1. Locate the task UI you must modify.

    For more information, see Locating a Task UI in the Tasks List.

  2. Make sure the status property is In Progress.
  3. On the WF/Task Editor toolbar, click the Publish icon.

    For more information, see Using the WF/Task Editor Toolbar.

    If you click Publish, then Siebel Tools prompts you to validate your task or to continue.

  4. Click Yes to continue.
  5. Make sure the status property is Completed.

    If Siebel Tools modifies the status from In Progress to Completed, then the task UI is available in the Siebel client.

Activating a Task UI

This topic describes how to activate a task UI.

To activate a task UI

  1. Log in to the Siebel Client.
  2. Navigate to the Administration - Business Process screen, and then the Task Deployment view.

    The Published Tasks list displays task UIs that are published from the repository tables. If you revise and publish a task UI, then Siebel CRM increments the repository version of the task. If you click the task name link, then Siebel CRM displays the child items of the task. These child items are the object definitions of the published task.

  3. In the Published Tasks list, query the Name field for the task UI you must activate.
  4. In the Published Tasks list, click Activate.

    Siebel CRM validates the format, and then modifies the deployment status of the task UI to Active. For more information, see About the Deployment Status

  5. Verify that the Deployment Status field of the Active Tasks list displays a value of Active for the task UI that you activated in Step 3.
  6. Optional. In the Active Tasks list, define deployment parameters for the task UI:
    1. In the Activation Date/Time field, set the activation date.

      It is not necessary to set an activation date or an expiration date. If you leave these fields empty, then the task UI is active and does not expire.

    2. In the Expiration Date/Time field, set the expiration date.
    3. Set the replication to None, unless you are deploying the task UI to a Siebel Mobile Web Client.

      If you are deploying the task UI to a Siebel Mobile Web Client, then see Replicating a Task UI to the Siebel Mobile Web Client.

About the Deployment Status

If the deployment status of the previous active version of a task UI exists when you activate a task, then Siebel CRM modifies the deployment status to Outdated. You can view this modification in the Active Tasks applet that Siebel CRM displays in the lower portion of the Task Deployment screen.

The deployment status of a deployed task can include one of the following values:

  • Active. A task UI that is active is the basis for a new task instance. Only one active version of a task with a specific name can exist.
  • Outdated. A task instance that is already in progress or that is in the inbox can continue to use the outdated object definition. A new instance does not use the outdated definition.
  • Inactive. If a task UI is inactive, then no new or paused task instance can use the inactive definition.

Adding a Responsibility to a Task UI

You publish and activate a task UI, specify the responsibilities that can run it, and then define the access rights that Siebel CRM must include in these responsibilities in the inbox. The Registered Task Administration view allows you to determine if a user can run, transfer, or delete a task UI. You must add the responsibility that Siebel CRM assigns to the user to the registered task so that this user can access this task UI.

If a user possesses the privileges that Siebel CRM requires to run a task UI, then this user also possesses the privileges required to access the views that this task UI uses.

You administer access control for a task UI in a way that is similar to how you administer access control for a view.

For more information, see Siebel Security Guide.

To add a responsibility to a task UI

  1. Log in to the Siebel client.
  2. Register the task UI:
    1. Navigate to the Administration - Application screen, and then the Tasks view.
    2. In the Registered Tasks list, click New.
    3. In the Task Name field, choose the task UI that you must register, and then click OK.

      Siebel CRM displays a list that includes deployed tasks. For more information, see Process of Deploying a Task UI.

  3. Add a responsibility to the task UI you registered in Step 2:
    1. Make sure the task UI you registered in Step 2 is still chosen in the Registered Tasks list.
    2. In the Responsibilities list, click New.
    3. In the Tasks dialog box, query for the responsibility that must include access to the task UI, and then click OK.

      If you typically log in with administrator privileges, then, for testing purposes, add the Siebel Administrator responsibility.

    4. In the Responsibilities list, make sure each of the following fields include a check mark:
      • Allow Delete. Allows the user to delete a paused task UI that Siebel CRM displays in the Universal Inbox.
      • Allow Transfer. Allows the user to transfer a paused task.

        The default value for each of these properties includes a check mark. For more information, see Resuming a Paused Task UI, and Universal Inbox.

  4. In the Registered Tasks list, click Clear Cache.
  5. Log out of the Siebel client.

Publishing and Activating a Task UI in Siebel Tools

You can publish and activate a task UI in Siebel Tools instead of publishing it in Siebel Tools and then activating it in the Siebel client. For more information, see Process of Deploying a Task UI.

To publish and activate a task UI in Siebel Tools

  1. Validate the task UI.

    For more information, see Validating a Task UI.

  2. Compile locked projects.

    For more information, see Preparing to Publish a Task UI.

  3. To publish and activate the task UI, do the following:
    1. Make sure the latest version of the task UI you are publishing is chosen in the Tasks list.
    2. In the WF/Task Editor Toolbar, choose the Publish/Activate button.

      For more information, see Using the WF/Task Editor Toolbar.

      Do not set the optional fields.

  4. Optional. For testing purposes, add the Siebel Administrator responsibility to the task UI.

    For more information, see Adding a Responsibility to a Task UI.

  5. If the Siebel client is open, then clear the cache, and then log out of the Siebel client.
Siebel Business Process Framework: Task UI Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.