Siebel Business Process Framework: Task UI Guide > Guidelines and Techniques for Developing a Task UI > Techniques to Improve the Usability of a Task UI >

Business Component Method Technique

The standard UI requires the user to click a button or to choose a menu item to call a section of business logic. This business logic typically calls a business component method and is not readily available as a business service method. The problem with this kind of user experience is that the user must possess knowledge about the following items:

• The user must click a button to run the logic
• The user must understand the result of clicking the button
• The user must understand the sequence to use to click multiple buttons

To avoid this complexity, task UI provides the following capabilities:

• Display unambiguous choices in the Siebel client
• Describe the result of clicking a button
• Provide backward navigation
• Enforce the sequence to use to click multiple buttons

You can provide the user with multiple choices in a task UI, one choice at a time:

1. The user makes a choice, and then clicks Next on the task playbar applet.
2. The task UI calls the business logic and in the correct order.
3. If an exception occurs, then the task UI displays an error dialog.
4. If an exception does not occur, then the task UI can display the next view.

Using the Business Component Method Technique

This topic describes how to use the business component method technique.

To use the business component method technique

1. If an adapter business service does not exist, then create one using values from the following table.

   Property	Value
   Class	CSSBCAdapterSvc

2. Make sure the value of the Business Component user property specifies the business component whose method or methods it is adapting.
3. Define a method with the same name as the business component method that Siebel CRM must call from the task UI.
4. Call the business component method from a business service step in the task UI.

   This business service step must reside downstream of a task view step so that the Next step flows to the business service step and calls the business component method.

   If you enable backward navigation to the selector view, and if this view displays an option that logically negates the underlying business logic that Siebel CRM performs, then you might need to adjust the flow of your business process so that it is compatible with backward navigation and the business logic.

Example of the Business Component Method Technique

The predefined Field Activity Invoicing task UI displays an option to automatically create an Invoice. The user clicks AutoInvoice in the Invoice applet to create this invoice in the standard UI. The predefined task calls an adapter business service method after the selector view. This task UI eliminates the requirement to use the AutoInvoice button in the Invoice applet.