Siebel Business Process Framework: Task UI Guide > Testing and Troubleshooting a Task UI > Adjusting Data Collection >

Disabling Transactions of a Task UI

In some testing scenarios it might be beneficial to temporarily disable transactions of a task UI. You can disable task transactions at the business component level and at the task level.

CAUTION:  Disabling task transaction can result in unpredictable behavior and must be thoroughly tested before use in production.

For more information, see Task Transaction.

To disable transactions of a task UI at the task level

1. Locate the task UI that you must modify.

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

2. Set the Transactional property to FALSE.

   If the Transactional property is set to FALSE, then task transaction is off, and updates on business components within the task UI are immediately committed to the base tables.

To disable transaction of a task UI at the business component level

1. If necessary, expose the Business Component User Prop object.

   For more information, see Exposing Object Types That Are Used to Develop a Task UI.

2. In Siebel Tools, in the Object Explorer, click Business Component.
3. In the Business Components OBLE, query the Name property for the business component that is involved with the task transaction.
4. In the Object Explorer, expand the Business Component tree, then click Business Component User Prop.
5. In the Business Component User Properties OBLE, query the Name property for Immediate Commit In Task.

   To view the predefined business components that include an Immediate Commit In Task user property, click the Flat tab in the Object Explorer, click Business Component User Prop, then query the Name property for Immediate Commit In Task.

6. Set the value property to TRUE.

   If the Value property for the Immediate Commit In Task user property is TRUE, then task transaction is off, and an update on this business component within a task UI is immediately committed to the base tables.

   Note that for a business component to be part of the task transaction, then task transaction must be turned on at both the business component level and at the task level.