Configuring the Immediate Post Changes Property of a Field

You can set the Immediate Post Changes property to one of the following values:

• TRUE. Siebel CRM immediately saves the field value to the Siebel Server. For example, if a user modifies a field value and then tabs to the next field in the same record, then Siebel CRM immediately saves this new value to the Siebel Server and then refreshes the data that it displays in the client. To do this, it makes a round trip to the Siebel Server and calls a PreSetFieldValue browser script event. For more information about this event, see Siebel Object Interfaces Reference.

• FALSE. Siebel CRM does not immediately save the field value to the Siebel Server. For example, if a user modifies a field value and then tabs to the next field in the same record, then Siebel CRM does not save this new value to the Siebel Server. The default value is FALSE.

Situations Where You Must Set the Immediate Post Changes Property to True

Setting the Immediate Post Changes property to TRUE might negatively affect performance. You typically set it to TRUE only to support the following configurations:

• Calculated field. For example, assume field B is a calculated field that uses values from field A. The Application Object Manager on the server does the calculation for a calculated field. If Siebel CRM modifies the value in field A, then it must do a server round trip to calculate and display the new value for field B. To allow this round trip, you must set the Immediate Post Changes property for field A to TRUE. You do not set it to TRUE for field B because Siebel CRM is not required to do a round trip if it modifies the value in field B.

  If the user modifies a value in a field, then Siebel CRM must run the code that the following event handlers contain on the Siebel Server:

  • BusComp_PreSetFieldValue performs a validation

  • BusComp_SetFieldValue causes some other action to occur after Siebel CRM validates a value

  If the Immediate Post Changes property is FALSE, then Siebel CRM does not run the code on the Siebel Server until the next time it performs a server round trip. If the PreSetFieldValue event finds a problem with the field value, and if the Immediate Post Changes property is FALSE, then Siebel CRM does not notify the user that a problem exists until the next time it performs a server round trip. For more information about event handlers, see Siebel Object Interfaces Reference.

• Constrained drop-down list. Assume the following constraints exists:

  • If field A = Y, then field B can contain Y1, Y2, Y3.

  • If field A = Z, then field B can contain Z1, Z2, Z3.

  In this example, Siebel CRM cannot populate the picklist for field B until the user chooses field A. To get the values for field B, it must perform a server round trip after the user chooses field A. To allow this round trip, you must set the Immediate Post Changes property for field A to TRUE. You do not set it to TRUE for field B because Siebel CRM is not required to do a round trip if it modifies the value in field B.