Share

Business Component User Properties

Siebel best practice recommends scripting should be used as a Last Resort, Do not write script if there is a way to implement the required functionality through configuration. Declarative configuration is easier to maintain and upgrade, leading to a lower total cost of ownership.

Preferred alternatives to scripting includes

• User properties• Field validation• Workflow• Personalization• Run-time events• State model

Siebel provides User Properties which are extremely valuable resource for implementing functionality that would have otherwise required scripting. The following User Properties has proven very useful. In this article we will have a brief discussion about few important and commonly used user properties. For complete list of user properties please refer to Siebel bookshelf. Remember that user properties are disabled for views with Admin Mode flag set to TRUE.

Read Only Field Makes a record read only based on the value of a field. Since the field that governs readonly behavior can be a calculated field, very complex logic can be implemented with this User Property. e.g. If STATUS is “Inactive” make REMARKS field read only. Field Read Only Field Sets specific fields in a Business Component to be read-only.  

On Field Update Invoke n This User Property allows you to invoke a Business Component method when the Specified field is updated. The value for On Field Update Invoke consists of three quoted parameters separated by a comma and a space, as follows: • “[FieldToCheck]”, “[BusCompName]”, “[MethodName]” • [MethodName] is invoked on the [BusCompName] Business Component when [FieldToCheck] is updated. If [FieldToCheck] is not defined, the method is invoked when the user saves the record. • You can optionally use a fourth parameter that defines a condition. If you define a condition, the method is only invoked if the condition evaluates to TRUE.

 

On Field Update Set n This User Property allows you to set the value of a field in the Business Component when another field is updated. The value for On Field Update Set consists of three quoted parameters separated by a comma and a space, as follows: • “[FieldToCheck]”, “[FieldToSet]”, “[Value]” • [FieldToSet] is set to [Value] when [FieldToCheck] is updated. If the Value parameter is not defined, [FieldToSet] is set to the value of [FieldToCheck]. An expression can optionally be used for the Value parameter. In the following example, the Done field is set using the expression when the Done Flag field is updated. • “Done Flag”, “Done”, “IIF ([Done Flag] =” “Y””,Today (), “” “”)” • Additionally, if you use an expression, you can include a fourth parameter that defines a condition.

Parent Read Only Field The parent Read Only Field can be used to make a child record read only based on the value of a field on the parent Business Component.

DeepCopy Allows child Business Components and respective child Business Ccomponents to be copied automatically when selecting the Copy option. Normally, Copy option only copies one level in the Business Object.

DeepDelete Normally, the Delete option only deletes one level. Deep Delete allows child Business Components and their respective child business components to be deleted automatically when selecting the Delete option.

 

Field User Prop – Required This User Property enables making a field required dynamically depending on other field values and expressions. If the evaluation returns true the field becomes Required. Note that this is defined at the field level, not the business component level. For example: • IIF ( [Forecast Mode] = 'Y', 'Y', 'N' ) • [Measure Unit] = LookupValue("IC_CAP_MEASURE_UNIT", "Amount")

NamedMethod This User Property has several different uses. It can be used to set field values when a specific field has been updated or to invoke a business service or even a workflow process. The User Property is used in conjunction with ‘On Field Update Invoke’ User Property. The following is an excerpt from “Siebel Developer Reference”: For setting a field value, the value consists of three quoted parameters separated by a comma and a space, as follows: • “[Name]”, “SET”, “[Field]”, “[Expression]” • When [Name] is called, the value of [Field] is set using [Expression]. For invoking a Business Component method, the value consists of four quoted parameters separated by a comma and a space, as follows: • “[Name]”, “[Action]”, “[BusComp]”, “[Method]” • When [Name] is called, [Method] is invoked on the [BusComp] Business Component based on the defined [Action]. For invoking a business service method, the value consists of five quoted parameters separated by a comma and a space, as follows: • “[Name]”, “[Action]”, “[BusComp]”, “[Service]”, “[Method]” • When [Name] is called, [Method] from the [Service] business service is invoked on the [BusComp] Business Component based on the defined [Action]. For invoking a Workflow with Input Parameters specifies the Workflow Process Manager as the Business Service and provides the list of Input Parameter – Value pairs within double and single quotes, as follows: • "[Name]", "INVOKESVC", "[BusComp]", "Workflow Process Manager", "RunProcess", "'ProcessName'", "'[Name of WF Process]'", "'[Parameter 1 Name]'", "’[Parameter 1 Value]", "'[Parameter 2 Name]'", "’[Parameter 2 Value]’" • The Parameter values can be dynamically read from the Business Component at Run time by using square brackets and only the single quotes as in the following example from the ‘SIS OM Asset Mgmt – Asset – Complex Header Billing’ Business Component User Property ‘Named Method 1’ o "NewProdSvc", "INVOKESVC", "SIS OM Asset Mgmt – Asset – Complex Header Billing", "Workflow Process Manager", "RunProcess", "'ProcessName'", "'SIS OM New Products & Services Process'", "'RowId'", "[Parent Account Id]", "'Account'", "[Parent Account]", "'Billing Account'", "[Billing Account]", "'Service Account'", "[Service Account]", "'Price List'", "[Parent Account Price List]"

 

Each of the user property needs to be covered in details, please refer Siebel bookshelf or wait for me 🙂

6 comments on “Business Component User Properties”

  1. Usm Reply

    You have said, “Each of the user property needs to be covered in details, please refer Siebel bookshelf or wait for me”, so I replied that we are waiting for you to come back with more exhaustive list of user properties:)

  2. Narsimha Narsimha Reply

    Hmmm, 🙂 Exploring bookshelf will best after this little intro of user properties. I will write about it in detail but you need to wait for that my friend.

  3. suresh Reply

    Hi Narsimha

    when we go for policies and when we go for runtime events in workflow invoking

  4. zhenhuang Reply

    hi,
    this is a very nice post. but i have some queries about when to used the double quote, two sets of double quote and single quote? why do you used it?

  5. Tara Reply

    Hi Narsimha,
    Thank you for the User Properties Intro.. for awhile I have been looking forward to your next articles on it. I am a BA and looking to pick-up some techno Siebel skills to be able to pitch myself for a more challenging role.
    Would be very helpful & great if you can share more.
    Tara

Leave A Reply

Your email address will not be published. Required fields are marked *

error: Content is protected !!