Required : A Field User Property

Siebel provides various ways in making any Field mandatory while saving the record. Some of the common ways we use in our daily Siebel implementation are :

a) "Required" property of BusComp's field. Setting this property to TRUE, made the field mandatory while saving the record.

b) "Required", a field user property which calculates an expression to decide whether the field should be mandatory or not. This is very useful for making field mandatory, conditionally.

c) Last one is writing script on "PreWriteRecord" event of business component.

I got the requirement to make "Spouse Name" field mandatory on the UI, when user checked the field "Married" to True.

The requirement sounds very simple but we should decide the best possible way to implement it. As I mentioned above, we can implement this requirement via two ways : first one is by writing code on PreWriteRecord event and the second one is by using "Required" field user property. Lets see the both implementation.

First Implementation - Scripting on PreWriteRecord() Event

if (this.GetFieldValue("Married") == "Y" && this.GetFieldValue("Spouse Name") == "")

{

TheApplication().RaiseErrorText("Spouse Name is a mandatory field");

}

Second Implementation - Required Field User Property

Create Field User Prop for "Spouse Name" field :

Name : Required

Value : IIf ([Married] = "Y", "Y", "N")

Compile the SRF by using one implementation at a time and see the difference.

Pros & Cons
1. Scripting solution is good if you need to show a customized message to the user, in case he forget to fill in the mandatory field. But scripting should be avoided as much as we can.

2. Using "Required" field user property is the recommended solution for such kind of scenarios.

.