Siebel Configuration Best Practices : Part 3

Siebel best practices for Immediate Post Changes.

In Siebel Configuration, the field level property Immediate Post Changes should be set to TRUE for a field when the data is to be posted to the server immediately when a user updates a field or whenever a  user steps out of the field. There are a lot of situations that when Immediate Post Changes = TRUE would be required for a field. However, if any of the cases cited below is not the case for the field then it should be set to FALSE.

1. If the field is the parent constraining field in a constrained picklist then Immediate Post Changes = TRUE should be set for the parent field. This will help ensure that the child picklist values are updated as soon as the value of the parent field is changed. 
2. Business Component event handler server script BusComp_PreSetFieldValue will not be invoked until unless Immediate Post Changes = TRUE for that particular field. 
3. For the BC User porperty On Field Update Set or On Field Update Invoked property, setting Immediate Post Changes = TRUE for the fields used in the calculations will ensure that the property is invoked as soon as the field changes that cause the property to be invoked are made. 
4. If there is any Siebel Vanilla fields that have Immediate Post Changes = TRUE configured out of the box, then it is advisable not to change this property as this property would be set to enable vanilla functionality for that Business Component field.
5. The Business Component event handler server script BusComp_SetFieldValue will not be invoked as soon as the field is updated unless Immediate Post Changes = TRUE for the field. If Immediate Post Changes = FALSE then when the field is updated it will not post the data to the server immediately so the BusComp_SetFieldValue event script will be "queued" until the data is posted on to the server. If many fields are updated prior to posting to the server then the BusComp_SetFieldValue event handler for each of these fields is queued. When data is finally posted to the server all the queued field BusComp_SetFieldValue event handler script is executed.
   Therefore if you need BusComp_SetFieldValue event handler to be invoked as soon as the field is updated then you need to set Immediate Post Changes = TRUE for the field. 
6. When you have a Field user property Field Read Only that uses other field(s) in the calculations, then these other fields need Immediate Post Changes = TRUE if you want to ensure that the read only rule will apply as soon as the dependent fields are updated. The read only rule will still work without setting Immediate Post Changes = TRUE however the read only rule will only apply after the data has been posted to the server. 
7. If any fields that are referenced in a Calculated Field do not have Immediate Post Changes set to TRUE then the Calculated Field value may not be updated as soon as the associated fields are updated. The Calculated Field will display updated value when the associated field data is posted to the server. 
8. If there is a Toggle Applet which is dependent on other field or fields then these field(s) should have Immediate Post Changes set to TRUE to ensure that the Toggle will occur as soon as the dependent field(s) are updated. 

Related Posts