Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Business Process Framework: Task UI Guide > Developing a Task UI > Developing a Task UI That Uses Transient Data > Guidelines for Using a Transient Business ComponentIf you use a transient business component, then use the following guidelines:
Storing Data Temporarily While Gathering the Information Required to Create a Complete RecordIf a task UI uses more than one view to get the information it requires to create a complete record, then you must use a transient business component. Task UI cannot insert a record in a business component until it collects a value for every field that the business component requires for a complete record. For example, assume you create a task UI that includes three separate views that do the following:
An opportunity record must include a value for each of the following required fields: You must use a transient business component to collect this information across views in the task UI. You can configure the task UI to copy data from the transient business component to the business component record when this task UI finishes. Using a Transient Business Component in a SubtaskA transient business component can include one or multiple instances for each context. You can configure Siebel CRM to use multiple instances when you create the transient business component. The context of the transient business component resides at the level of the subtask. The subtask and the parent task do not share the same instance of the transient business component even if the subtask uses the same transient business component that the parent task UI uses. If no instance of a transient business component exists in the current context, then Siebel CRM creates a new instance when it queries the transient business component. For more information, see Creating a Subtask Step. Using a Transient Business Component with a Commit StepSiebel CRM erases transient data that resides in the S_TU_LOG table when a commit step saves data. You can configure Siebel CRM to create a new instance of the transient business component and display it in a task view step after Siebel CRM clears the commit data and the transient data. Siebel CRM does not clear new data from the S_TU_LOG table. If more modifications occur in the transient business component, then Siebel CRM updates the same record in the S_TU_LOG table. It does not clear the older data and it does not create a new record until it issues a commit. For more information, see Creating a Commit Step. Using the Defer Write Record Property of a Siebel Operation Step Instead of a Transient Business ComponentThe Defer Write Record property on a Siebel operation step postpones a write operation until the task flow encounters a subsequent commit step. If the only data storage requirement for your task UI is to store the data that is involved with a Siebel operation step, then you can use the Defer Write Record property instead of a transient business component and task applet. For more information, see About the Defer Write Record Property. |
![]() ![]() |
Siebel Business Process Framework: Task UI Guide | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |