Reader small image

You're reading from  Oracle Siebel CRM 8 Developer's Handbook

Product typeBook
Published inApr 2011
Reading LevelIntermediate
Publisher
ISBN-139781849681865
Edition1st Edition
Languages
Concepts
Right arrow
Author (1)
Alexander Hansal
Alexander Hansal
author image
Alexander Hansal

Alexander Hansal has worked as an IT professional in small, medium, and global corporations. Since 2001, Alexander works as a technical instructor and consultant for Siebel CRM and Oracle Business Intelligence in Europe. He enjoys teaching, and shares his knowledge and expertise in his classes at Oracle University and in his weblog, http://siebel-essentials.blogspot.com/
Read more about Alexander Hansal

Right arrow

Chapter 13. User Properties

Many business requirements are very detailed and complex. For example, the end user community could demand that one field is updated automatically when another field has been changed. To solve this kind of requirement in Siebel CRM, developers can define so-called user properties as an extension to the standard properties of object types such as business components, fields, and applets. In this chapter, we will discuss the following topics:

  • Understanding user properties

  • Business component and field user properties

  • Applet, control, and list column user properties

  • Viewing user properties

Understanding user properties


User properties are child object types that are available for the following object types in the Siebel Repository:

  • Applet, Control, List Column

  • Application

  • Business Service

  • Business Component, Field

  • Integration Object, Integration Component, Integration Component Field

  • View

To view the User Property (or User Prop as it is sometimes abbreviated) object type we typically have to modify the list of displayed types for the Object Explorer window. As discussed in the previous chapter, this can be achieved by selecting the Options command in the View menu. In the Object Explorer tab of the Development Tools Options dialog, we can select the object types for display as shown in the following screenshot:

In the preceding example, the Business Component User Prop type is enabled for display.

After confirming the changes in the Development Tools Options dialog by clicking the OK button, we can for example navigate to the Account business component and review its existing user...

Business component and field user properties


On the business layer of the Siebel Repository, user properties are widely used to control specialized behavior of business components and fields. The following table describes the most important user properties on the business component level. The Multiple Instances column contains Yes for all user properties that can be instantiated more than once per parent object:

Applet, control, and list column user properties


The Applet object type provides user properties on the applet level itself as well as on the control and list column level (for list applets only).

The following table describes some of the most important applet user properties:

User Property Name

Description

Multiple Instances

Active Field

Active Value

These two user properties define the name of a business component field and a value of that field. When the field has the value defined in the Active Value user property then the record is considered Active and can be updated. Otherwise, the record is considered Inactive and cannot be updated.

No

Admin NoDelete

Admin NoUpdate

When the value of these user properties is set to Y, the business component prevents deletions or updates (respectively) even when the business component is in Admin mode.

No...

View user properties


The only officially documented user property for the View object type is DefaultAppletFocus. The value of this user property is the name of one of the view's applets. The applet will have focus when the view is loaded.

Summary


User properties are a powerful resource for defining special application behavior and business logic. They are provided as an alternative to writing custom script code by Oracle engineering.

Because user properties are often limited to certain classes, in the case of business components and applets, their functionality is not always easy to understand.

In this chapter, we introduced the most important user properties for business components, fields, applets, controls, list columns, and views.

In the next chapter, we will learn how to support navigation concepts such as drilldowns, applet toggles, and the thread bar.

lock icon
The rest of the chapter is locked
You have been reading a chapter from
Oracle Siebel CRM 8 Developer's Handbook
Published in: Apr 2011Publisher: ISBN-13: 9781849681865
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
undefined
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime

Author (1)

author image
Alexander Hansal

Alexander Hansal has worked as an IT professional in small, medium, and global corporations. Since 2001, Alexander works as a technical instructor and consultant for Siebel CRM and Oracle Business Intelligence in Europe. He enjoys teaching, and shares his knowledge and expertise in his classes at Oracle University and in his weblog, http://siebel-essentials.blogspot.com/
Read more about Alexander Hansal

User property

Description

CanInvokeMethod: methodname

This user property allows controlling whether a button or menu item on the applet is enabled (clickable) or disabled (grayed out and not clickable). The name of the method invoked by the button or by the command behind the menu item is specified as the second part of the name (after a colon and a space).

The value of this user property can be either a string—TRUE or FALSE or eventually Y or N—or an expression that must evaluate to TRUE or FALSE.

Example:

Name: CanInvokeMethod: CancelFunction

Value: [Freeze Flag] <> "Y"

Explanation:

Buttons or menu items exposing the CancelFunction method will only be clickable when the value of the Freeze Flag field is not...