Task Based UI and its Usage

Posted by Vimarsh Ganju
Comments (3)
June 30th, 2008

In all the Applications a particular task requires performing several steps to complete it which leads to common issues. Some issues are as follows:

  • Users may not be familiar with the sequence of steps
  • Users may inadvertently skip a step
  • Users often require additional training to complete the task.

Many clients prefer implementing a user interaction style that assists end users in completing such tasks.
The latest version Siebel 8.0 provides a feature called as Task Based UI, which enables us to use wizard-like interface( in this we can Use a wizard- like interface) to guide users through steps in a task. This helps in completing the tasks in (leads to complete some steps of a task in) a prescribed order. It supports forward and backward navigation through a sequence of views. In addition to this we can use the pause facility.
In TBUI one can implement the Branching conditions based on the users input. This can be achieved with the use of Transient BC (TBC). The mechanism behind TBC is that-data is collected and used during the execution of a task but not saved afterwards i.e. Transient data disappears when the task ends.
I worked upon a scenario i.e. Quote Generation which processes the Quotation, Opportunity and Account Information for each and every Quote. Following is the description
The Process starts with the enquiry raised by the customer to the Customer Service Representative (CSR) for the same he/she will

  • Create an Opportunity by adding a Customer Account.
  • Create the Product for the same Opportunity from Administration – Products.
  • Create an Quote for the Opportunity.
  • Add the Price list for the Quote; this price should be available for the Line Items (product).
  • Generate the Quote information along with the Opportunity and Account.

Finally that will be delivered to the customer (Account Holder) through mail.

Task, Task Group & Task Pane View: I created a new “Task Group” & a “Task”. Then added that “Task” to the “Task Group”. Later added the “Task Group” to the “View Task Group” named “Task Pane View”.

Views & Applets

I used vanilla Applets such as – Opportunity Entry Applet, Product Form Applet, Quote List Applet, Recipient List Applet etc. Made new Objects by copying the above mentioned applets and then used them on the corresponding Task Views. Also I inactivated the fields in the applet which was not supposed to be displayed.

Configuring TBC & Auto Quote functionality:
There is no change in the BC’s. I used Siebel provided “Auto Quote” functionality for the Quote creation. Due to the requirement of giving a choice to add multiple recipients for the Correspondence I created a Transient Business Component.

Adhoc functionality: All the Adhoc functionality which I used here was vanilla provided.

Pulling Data from Quote to Recipient:The biggest challenge was to pull Quote fields in Recipient BC through indirect Joins. First I created Link between Quote and Correspondence then with the help of Link Specification I pulled the Quote Row Id in the Correspondence then to the Recipient BC. Now by configuring a join in Recipient BC and Quote BC using the pulled Quote Row Id, I pulled all the desired fields of Quote BC.The Below Diagram will help you to understand it more clearly,

Task Based UI

The Final Version of Task flow was looking like the below figure:

Task Based UI

Finally, everything shaped up well and I delivered my first Task Based UI successfully on time. Please put your comments / suggestions.

Inputs from Abhinav A.

Comments (3)

Raghu Rao - November 16th, 2009

Hi I wanted to confirm that we can develop TBUI spanning across multiple Business Objects like SR, Quote and Opportunity.

vishnu - June 1st, 2009

Thank you

vishnu - June 1st, 2009


Comments are closed.