Applet NoDataHide

CanInvokeMethod:

EnableStandardMethods defult applet method default focus edit disable new record named method

This user property hides the applet when it contains no data.

You can inactivate and modify the values for this user property. You can also create new instances of this user property as ne

This user property allows you to enable and disable methods, such as buttons, declaratively at the applet level. It is easier to Name CanInvokeMethod: MethodName Value Value or expression that returns TRUE or FALSE

If this user property is declared on an applet, end users can use the applet to perform the record manipulation operations wit value=methodname filed or control name applicatio name

his user property as needed

plet level. It is easier to use than PreCanInvokeMethod scripting and in many cases can be used instead.

pulation operations within a task view that they can within an ad hoc view, such as performing queries, advancing the record pointer, edi

advancing the record pointer, editing multiple records at once and so on.

Active Field

The Active Field and the Active Value user properties together determine whether For a given business component, the Active Field user property specifies the field on See also Active Value. Value:

The value of the Active Field user property must be the name of a field on the curren

If the business component has the Active Value user property and its value is Y, or if t

For example, the value of the Active Field user property on the Quote business comp

Alternatively, the value of the Active Field user property on the Fund business compo Usage:

You can inactivate this user property or modify its values. You cannot create more th Active Value The Active Value and the Active Field user properties together determine whether a For a given business component, the Active Field user property specifies the field on See also Active Field. Value: Y or N.

To use the Active Value user property, you must also set the Active Field user proper

For example, the value of the Active Field user property on the Quote business comp

Alternatively, the default value of the Active Field user property on the Fund busines Usage:

You can inactivate this user property or modify its values. You cannot create more th

Admin Mode Field

The Admin Mode Field user property provides access to the current value of th

Although the Admin Mode Flag is a View property, the business component ob

In Admin mode, updating, inserting, deleting, and merging records is permitted

For information on Admin Mode functionality, see Security Guide for Siebel Bu Value: The value of the Admin Mode Field user property must be the name of a field

For example, for a given business component, create a calculated field, as desc Usage:

This user property is intended for use with script to identify whether a busines function BusComp_NewRecord () { var isAdmin = this.GetFieldValue("IsAdminMode"); var WshShell = COMCreateObject("WScript.Shell"); WshShell.Popup(isAdmin); }

You can inactivate this user property or modify its value. You can create new in

Admin NoDelete

This user property prevents deleting records when a view, and thus its busines

Administrative views often have their Admin Mode Flag property set to TRUE t

For information on Admin Mode functionality, see Security Guide for Siebel Bu Value: Y or N.

The value of this user property defaults to N if the user property is not defined Usage:

You can inactivate this user property or modify its value. You can create new in Admin NoUpdate

This user property prevents updating of records when a view, and thus its busi

Administrative views often have their Admin Mode Flag property set to TRUE t

For information on Admin Mode functionality, see Security Guide for Siebel Bu Value:

Y or N.

The value of this user property defaults to N if the user property is not defined Usage:

You can inactivate this user property or modify its value. You can create new in All Mode Sort

Standard Siebel application behavior is to override the sort specification on vie

Aspect BC NoInsert: [Aspect]

If Aspect BC NoInsert: Aspect is defined, and the current aspect is A NOTE: To use Aspect BC NoInsert: Aspect, you need to make sure t

Aspect BC Readonly: [Aspect] Aspect Child BC ReadOnly: [Aspect] BC Read Only Field

If F176Aspect BC ReadOnly: Aspect is defined, and the current aspe

If Aspect Child BC ReadOnly: Aspect is defined, and the current asp

Specifies a TRUE/FALSE field in the record that, when TRUE, causes

Setting the Admin Mode Flag property to TRUE circumvents a Read Currency Field n

This user property allows you to specify the name of a field that holds currency Value:

The value for the Currency Field n user property must be the name of a field o Usage:

When the currency code is changed, a currency exchange operation is perform

You can inactivate and modify the values for this user property. You can also c DataCleansing Field n Deep Copy n

Specifies a correspondence between a field name in the Siebel Firstlogic Conne

Allows child business components and respective child business components t To use Deep Copy, do the following:

In the parent business component, create a user property for each child busine Name: Deep Copy 1 Value: [Child BusComp Name] Name: Deep Copy 2 Value: [Child BusComp Name]

Add a multivalue link in the parent business component for each child business Create a multivalue field in the parent business component from each child bu Set the Field No Copy attribute in the multivalue link to TRUE or an SQL error o Each business component in the Deep Copy chain takes care of its own childre

There is an analogous Deep Delete user property to do a deep cascade delete. Deep Copy/Delete Link: [Business Component]

The value of this business component user property mu Usage:

For example, to specify a link to apply to deep copying o

You can inactivate or modify the values for this user pro

CAUTION: Before you inactivate any predefined instanc Deep Delete n

Normally, the Delete option only deletes one level. Deep Delete allows child b

Create a user property for each child business component to be included in the Name: Deep Delete 1 Value: [Child BusComp Name] Name: Deep Delete 2 Value: [Child BusComp Name]

Add a multivalue link for each child business component. Set the No Delete use TRUE: allows deep delete for child business component FALSE: does not allow deep delete for child business component

Create a multivalue field in the parent business component, using the multival

This is analogous to the Deep Copy user property. Use Deep Delete to do a dee Default Aspect Field Read Only Field: [Field Name] Sets specific fields in a business component to be read-only.

The Value property contains a field that is Boolean. When TRUE, th

MVG Set Primary Restricted: [Visibility MVL Name]

Setting this user property to FALSE allows th

If this user property is not set, only Siebel A Usage:

MVG Set Primary Restricted: [Visibility MVL where

[Visibility MVL Name] is the value of the Vis

For example, if you want to allow sales repr

Create a user property for the Contact Busin Position is the value of Visibility MVLink for Set the value of MVG Set Primary Restricted Named Method n Syntax:

The value you provide for the Named Method user property depen

For setting a field value, the value consists of three quoted parame [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 f [Name], "[Action]", "[BusComp]", "[Method]"

When [Name] is called, [Method] is invoked on the [BusComp] bus

For invoking a business service method, the value consists of five q [Name], "[Action]", "[BusComp]", "[Service]", "[Method]"

When [Name] is called, [Method] from the [Service] business servic

You can optionally append an additional parameter that defines an Usage:

You can create additional instances of this user property as needed

The values for [Action] are: INVOKE, INVOKESEL, INVOKEALL, INVOK

See the "Siebel Developer's Reference" for more information abou

NoDelete Field

This user property allows you to restrict the deletion of records bas

Syntax:

The value of the NoDelete Field user property must be the name o Usage: You can inactivate or modify the values for this user property. You On Field Update Invoke n

This user property allows you to invoke a business component me Syntax:

The value for On Field Update Invoke consists of three quoted para [FieldToCheck], "[BusCompName]", "[MethodName]"

[MethodName] is invoked on the [BusCompName] business compo

You can optionally use a fourth parameter that defines a condition Usage:

You can create additional instances of this user property as needed On Field Update Set n

This user property allows you to set the value of a field in the busin

The value for On Field Update Set consists of three quoted parame [FieldToCheck], "[FieldToSet]", "[Value]"

[FieldToSet] is set to [Value] when [FieldToCheck] is updated. If the

An expression can optionally be used for the Value parameter. In th Done Flag, "Done", "IIF ([Done Flag] = ""Y"", Today (), """")"

Additionally, if you use an expression, you can include a fourth para

NOTE: If you use an expression, it must evaluate to the data type o

Agreement Start Date, "Name", "ToChar([Agreement Start Date]) + Usage:

You can create additional instances of this user property as needed

Parent Read Only Field Recursive Link

Specifies a TRUE/FALSE test business component/field combination in the pare

The Deep Copy, Deep Delete, and Update Foreign Key Field user pr Value

The value of this business component user property must be the na Usage

For example, to delete catalog subcategories when a category is de

NOTE: The convention for naming links is parent business compon You can inactivate or modify the values for this user property. You State Model

This user property allows you to make additional business compon Value: The value for the State Model user property is either Y or N. Usage:

Setting the State Model user property to Y adds the business comp

To add business components to the State Model business compone

In Siebel Tools, go to the business component (for example, Accoun Add a record called "State Model" with a value of "Y" (do not includ Recompile the .srf file. Re-enter the Siebel application and navigate to Site Map > Workflo Add a record to the State Model List Applet. All of the business com When you select the appropriate one and navigate to Field Name, The State Name values populate the State Model depending on the

NOTE: Administration of the List of Values is separate from the Sta

Once you have added business components to the MVG Applet, yo For more information about the State Model, see the Applications Sequence Field

This user property allows you to define a sequence field for a business compon Value:

The value for the Sequence Field user property must be the name of the field (

Usage: This user property is used to configure a sequence field to create a sequential

For new record and copy record events, this user property specifies a field on t

NOTE: When defining a Sequence Field user property, set the Insert Position p

NOTE: Configuring a sequence field on a business component requires several

For information on how a new record with a sequenced field is numbered, see

This user property allows you to specify whether to generate sequence numbe Sequence Use Max See also Sequence Field. Value:

A value of Y causes the sequence number of a new or copied record to be gene If this user property is not defined on the business component or if this user pr Usage:

This user property determines whether the sequence number generated is bas

For example, to define a field Line Number as a sequence field for which new a

Sequence Field with value Line Number Sequence Use Max with value Y NOTE: Configuring a sequence field on a business component requires several

es together determine whether a record is active. An active record can be updated. A record that is not active cannot be updated.

er property specifies the field on the business component that is the active flag. The Active Value user property specifies how to intepret

the name of a field on the current business component, not enclosed in quotes. The named field must be the active flag for the business c

property and its value is Y, or if the Active Value user property is not defined, then a record is active if the value of its active flag is Y. If th

erty on the Quote business component is Active. The Active Value user property is not defined on Quote. Thus a record is active if its Activ

erty on the Fund business component is Locked Flag. The value of its Active Value user property is N. Thus a record is active if its Locked F

alues. You cannot create more than one instance of this user property for a business component.

s together determine whether a record is active. An active record can be updated. A record that is not active cannot be updated.

er property specifies the field on the business component that is the active flag. The Active Value user property specifies how to intepret

o set the Active Field user property on the business component to specify the field that contains the active flag. If the Active Value user pr

erty on the Quote business component is Active. The Active Value user property is not defined on Quote. Thus a record is active only if its

ser property on the Fund business component is Locked Flag. The value of its Active Value user property is N. Thus a record is active only i

alues. You cannot create more than one instance of this user property for a business component.

s access to the current value of the business component's Admin Mode Flag.

perty, the business component object has a corresponding internal Admin Mode Flag property. At runtime, the business component inhe

and merging records is permitted, independent of those property values on the business component.

, see Security Guide for Siebel Business Applications and Configuring Siebel Business Applications.

erty must be the name of a field on the current business component, not enclosed in quotes. The named field should be an active calcula

, create a calculated field, as described above, and name it IsAdminMode. This is the naming convention for such a field, although the nam

ript to identify whether a business component is currently in Admin mode. The following simple example displays Y if the business compo

fy its value. You can create new instances of this user property, but you should not create more than one instance for a business compone

when a view, and thus its business component, are in Admin mode.

Mode Flag property set to TRUE to allow administrators to insert, update, delete, and merge records on business components that are se

, see Security Guide for Siebel Business Applications and Configuring Siebel Business Applications.

f the user property is not defined on the business component.

fy its value. You can create new instances of this user property, but you should not create more than one instance for a business compone

ds when a view, and thus its business component, are in Admin mode.

Mode Flag property set to TRUE to allow administrators to insert, update, delete, and merge records on business components that are se

, see Security Guide for Siebel Business Applications and Configuring Siebel Business Applications.

f the user property is not defined on the business component.

fy its value. You can create new instances of this user property, but you should not create more than one instance for a business compone

rride the sort specification on views with certain visibility types to force it to ORDER BY the standard user key. The All Mode Sort user pro

efined, and the current aspect is Aspect, the user cannot insert new records when the value of Field Name is Y. : Aspect, you need to make sure that the value [Field Name] (normally a calculated field) will not be changed when the user steps to a diff

t is defined, and the current aspect is Aspect, the current record will become read-only when the value of Field Name is Y.

ct is defined, and the current aspect is Aspect, the current record's child business components will become read-only when the value of F

e record that, when TRUE, causes the current record to become read-only.

perty to TRUE circumvents a Read Only field defined at the business component object type user property.

ame of a field that holds currency data.

rty must be the name of a field on the business component.

cy exchange operation is performed on the data in the specified field and the value of the field is updated.

this user property. You can also create new instances of this user property.

ame in the Siebel Firstlogic Connector and a field name in the Siebel application. Used for Siebel Data Quality, which performs address ver

tive child business components to be copied automatically when selecting the Copy option. Normally, Copy option only copies one level.

ser property for each child business component to be included in the deep copy. The child business component user properties are:

omponent for each child business component. ss component from each child business component. lue link to TRUE or an SQL error occurrence: "A Duplicate Record Exists." hain takes care of its own children. So the parent business component will have Deep Copy properties for each of its direct children, and e

erty to do a deep cascade delete. Typically, use Deep Copy and Deep Delete together.

ess component user property must be the name of a link between the current (parent) business component and the child business compo

y a link to apply to deep copying or deep deleting of the revenues associated with an opportunity, add the user property Deep Copy/Dele

modify the values for this user property. You can also create new instances of this user property.

inactivate any predefined instances of this user property in a production environment, do thorough planning and testing to confirm that

level. Deep Delete allows child business components and their respective child business components to be deleted automatically when se component to be included in the deep delete. The child business component user properties are:

omponent. Set the No Delete user property value to:

usiness component

ss component, using the multivalue link. This field is usually not displayed on the screen but needs to be present on the business compone

erty. Use Deep Delete to do a deep cascade delete. Typically, use Deep Copy and Deep Delete together.

mponent to be read-only.

d that is Boolean. When TRUE, the field specified by [fieldname] in the current record is read-only.

user property to FALSE allows the Primary team member to be altered by someone other than the Manager or Siebel Administrator.

property is not set, only Siebel Administrators (in Admin mode) and Managers (in Manager view mode) have the ability to change the Prim

rimary Restricted: [Visibility MVL Name],

MVL Name] is the value of the Visibility MVLink property of the BusComp View Mode child object of the business component for which yo

e, if you want to allow sales representatives to set the primary sales team members for contacts:

er property for the Contact Business component called MVG Set Primary Restricted: Position. the value of Visibility MVLink for the Sales Rep view mode for Contact. ue of MVG Set Primary Restricted: Position to FALSE.

med Method user property depends on the action you want to perform. consists of three quoted parameters separated by a comma and a space, as follows:

of [Field] is set using [Expression].

nt method, the value consists of four quoted parameters separated by a comma and a space, as follows:

, "[Method]"

is invoked on the [BusComp] business component based on the defined [Action]. For a list of actions, see Table 8.

ethod, the value consists of five quoted parameters separated by a comma and a space, as follows:

, "[Service]", "[Method]"

from the [Service] business service is invoked on the [BusComp] business component based on the defined [Action]. For a list of actions, s

itional parameter that defines an expression. If you use a business service action, the expression is passed as a property set, so you must

es of this user property as needed. If you have more than one instance of this user property for a business component, each instance is ex

E, INVOKESEL, INVOKEALL, INVOKESAVE, INVOKESVC, INVOKESVCSEL, INVOKESVCALL, INVOKESVCSAVE

ence" for more information about these actions.

estrict the deletion of records based on the value of the specified field. When you specify a field in this user property, the business compo

ser property must be the name of a field in the business component.

alues for this user property. You can also create new instances of this user property as needed.

nvoke a business component method when the specified field is updated.

oke consists of three quoted parameters separated by a comma and a space, as follows:

", "[MethodName]"

[BusCompName] business component when [FieldToCheck] is updated. If [FieldToCheck] is not defined, the method is invoked when the

rameter that defines a condition. If you define a condition, the method is only invoked if the condition evaluates to TRUE.

es of this user property as needed. If you have more than one instance of this user property for a business component, they are executed

et the value of a field in the business component when another field is updated.

consists of three quoted parameters separated by a comma and a space, as follows:

[FieldToCheck] is updated. If the Value parameter is not defined, [FieldToSet] is set to the value of [FieldToCheck].

sed for the Value parameter. In the following example, the Done field is set using the expression when the Done Flag field is updated.

g] = ""Y"", Today (), """")"

ion, you can include a fourth parameter that defines a condition.

must evaluate to the data type of the targeted field. In the following example, the ToChar function is used to convert the date to a string

ToChar([Agreement Start Date]) + [Agreement Type]"

es of this user property as needed. If you have more than one instance of this user property for a business component, they are executed

ent/field combination in the parent chain (parent, grandparent, and so on) that, when TRUE, causes the target business component to be

Update Foreign Key Field user properties are used to copy or delete records of child business components when a record of the current (

nent user property must be the name of an existing link between the current (parent) business component and itself.

bcategories when a category is deleted, you could use Deep Delete with the Recursive Link user property set to Catalog Category/Catalog

g links is parent business component/child business component, but a link name does not have to follow this convention. Thus the name o

alues for this user property. You can also create new instances of this user property as needed, but you should not create more than one

make additional business components accessible to the State Model business component Multi-Value Group applet.

r property is either Y or N.

erty to Y adds the business component to the State Model business component Multi-Value Group applet.

he State Model business component multi-value group applet component (for example, Account) that you want to add to the state model and navigate to the Business Component User Prop object. with a value of "Y" (do not include the quotation marks).

d navigate to Site Map > Workflow Administration > State Models > State Models. ist Applet. All of the business components you added in Siebel Tools should appear in the business component Name Multi-Value Group. one and navigate to Field Name, the MVG applet that pops up includes all of the fields for the previously selected business component. he State Model depending on the values listed in the List of Values (Site Map > Application Administration > List of Values).

of Values is separate from the State Model. However, only values that appear in the LOV can be used in the State Name field. For Account

mponents to the MVG Applet, you can create the State Model rules that Siebel Workflow enforces.

tate Model, see the Applications Administration Guide

uence field for a business component.

y must be the name of the field (typically Line Number or Sequence Number) in the business component that corresponds to the sequen

ence field to create a sequential auto-generating line number on new record and copy record events. A sequence business component m

user property specifies a field on the business component whose value is a number in a sequence that is auto-generated. A sequence busi

property, set the Insert Position property to LAST for the applets that display records from the numbered detail business component. Leav

ness component requires several tasks to be completed. For detailed information on creating sequence fields, see Configuring Siebel Busi

sequenced field is numbered, see also Sequence Use Max.

her to generate sequence numbers for the business component based on the maximum sequence number.

a new or copied record to be generated as the maximum of the existing sequence numbers + 1. iness component or if this user property has a value of N, then the sequence number of a new or copied record is generated as the seque

equence number generated is based upon the current record position or the maximum sequence number.

a sequence field for which new and copied records are assigned a the maximum of the existing sequence values + 1, you would have to a

ness component requires several tasks to be completed. For detailed information on creating sequence fields, see Configuring Siebel Busi

t active cannot be updated.

roperty specifies how to intepret the value of the flag.

e the active flag for the business component.

he value of its active flag is Y. If the value of the Active Value user property is N, then a record is active if the value of its active flag is N.

e. Thus a record is active if its Active field value is Y.

us a record is active if its Locked Flag field value is N-that is, when it is unlocked.

ctive cannot be updated.

roperty specifies how to intepret the value of the flag.

ve flag. If the Active Value user property is also defined and its value is Y, or if the Active Value user property is not defined, then a record

e. Thus a record is active only if its Active field value is Y. is N. Thus a record is active only if its Locked Flag field value is N-that is, when it is unlocked.

me, the business component inherits the value of the Admin Mode Flag from the current view.

d field should be an active calculated field of type DTYPE_BOOL with a value of "".

for such a field, although the name is not restricted. Add the Admin Mode Field user property on the business component with a value o

e displays Y if the business component is currently in Admin mode; otherwise, it displays N.

e instance for a business component.

business components that are set to disallow some or all of these operations in typical views. Thus, setting the Admin NoDelete user pro

e instance for a business component.

business components that are set to disallow some or all of these operations in typical views. Thus, setting the Admin NoUpdate user pro

e instance for a business component.

er key. The All Mode Sort user property determines whether or not the Siebel application overrides the sort specification and, if so, determ

nged when the user steps to a different record; otherwise runtime behavior will confuse the end user. Improper configuration will make i

of Field Name is Y.

me read-only when the value of Field Name is Y.

uality, which performs address verification, name and address standardization, and duplicate record identification, in real-time and batch

opy option only copies one level. This feature allows multiple levels to be copied like a cascade copy.

ponent user properties are:

or each of its direct children, and each child business component will have Deep Copy properties for each of the relevant grandchildren.

nent and the child business component specified by the Buscomp parameter.

he user property Deep Copy/Delete Link: Revenue with value Opportunity/Revenue to the Opportunity business component. Opportunity

nning and testing to confirm that the child records that are to be no longer copied or deleted are those you intended, and that records of be deleted automatically when selecting the Delete option. This feature allows multiple levels to be deleted like a cascade delete.

present on the business component.

nager or Siebel Administrator.

have the ability to change the Primary team member on opportunities, accounts and contacts.

business component for which you want to allow or restrict setting the primary.

ned [Action]. For a list of actions, see Table 8.

ed as a property set, so you must use name value pairs rather than an array of strings ("NameExpr", "ValueExpr").

ss component, each instance is executed sequentially by number (for example, On Field Update Invoke 1, then On Field Update Invoke 2,

user property, the business component will not allow records to be deleted that have a value of Y in the specified field.

the method is invoked when the user saves the record.

evaluates to TRUE.

ss component, they are executed sequentially by number (for example, On Field Update Invoke 1, then On Field Update Invoke 2, and so o

dToCheck].

he Done Flag field is updated.

sed to convert the date to a string before concatenating with another string and setting value of the field.

ss component, they are executed sequentially by number (for example, On Field Update Set 1, then On Field Update Set 2, and so on). If t

target business component to become read-only.

nts when a record of the current (parent) business component is copied or deleted. If the parent and child are the same business compon

nt and itself.

y set to Catalog Category/Catalog Category.

this convention. Thus the name of a link specified by Recursive Link may have different names on either side of the slash; for example, A

should not create more than one instance of this user property on a business component.

ss Component User Prop object.

ponent Name Multi-Value Group. y selected business component. on > List of Values).

the State Name field. For Account, all the LOV names are ACCOUNT_STATUS with different display values associated with each.

nt that corresponds to the sequence number column in the underlying table.

sequence business component must be defined in the business object. auto-generated. A sequence business component must also be defined in the business object.

d detail business component. Leaving the Insert Position property blank can cause unexpected behavior in the line numbers generated in

fields, see Configuring Siebel Business Applications.

record is generated as the sequence number of the current record + 1. Other records are renumbered, if necessary.

ce values + 1, you would have to add the following user properties to the business component:

fields, see Configuring Siebel Business Applications.

f the value of its active flag is N.

perty is not defined, then a record is active if the value of its active flag is Y. If the value of the Active Value user property is N, then a reco

usiness component with a value of IsAdminMode.

ting the Admin NoDelete user property on a business component typically means that records cannot be deleted in any view.

ting the Admin NoUpdate user property on a business component typically means that records cannot be updated in any view.

sort specification and, if so, determines the sort (if any) that is applied to the business component for the affected views.

mproper configuration will make inserts dependent on the state of current records, which is most likely not what you want.

ntification, in real-time and batch modes.

h of the relevant grandchildren.

business component. Opportunity is the parent and Revenue is the child business component of the Opportunity/Revenue link.

you intended, and that records of other business components related to those child records are not adversely affected.

eted like a cascade delete.

1, then On Field Update Invoke 2, and so on). If there is only one such user property, then no number is required.

specified field.

On Field Update Invoke 2, and so on). If there is only one such user property, then no number is required.

Field Update Set 2, and so on). If there is only one such user property, then no number is required.

ld are the same business component, then the link that defines the parent/child relationship must be specifed by the Recursive Link user

r side of the slash; for example, Action/Action - Deep. The requirement that must be met is that the parent and child business componen

es associated with each.

in the line numbers generated in the applet.

if necessary.

ue user property is N, then a record is active if the value of its active flag is N.

e deleted in any view.

e updated in any view.

e affected views.

not what you want.

portunity/Revenue link.

ersely affected.

pecifed by the Recursive Link user property.

ent and child business components of the link must be the same business component.

Aspect Default Value: [Aspect]

This user property allows you to specify whether to generate sequence nu See also Sequence Field. Value:

A value of Y causes the sequence number of a new or copied record to be If this user property is not defined on the business component or if this us Usage:

This user property determines whether the sequence number generated is

For example, to define a field Line Number as a sequence field for which n

Sequence Field with value Line Number Sequence Use Max with value Y NOTE: Configuring a sequence field on a business component requires sev Display Mask Char Required

Masks credit card numbers. Create a calculated field with no calculation an

This user property allows you to make the parent field a required field und Value: The value of the Required user property is an expression. Usage:

You specify the condition by defining a calculated expression for the value Text Length Override

This user property allows you to specify that the text length of the field, ra Value:

The value for the Text Length Override user property is either TRUE or FAL Usage:

When this user property is set to TRUE, the Text Length property of the fie

This user property replaces the Field Length user property in older version

her to generate sequence numbers for the business component based on the maximum sequence number.

a new or copied record to be generated as the maximum of the existing sequence numbers + 1. iness component or if this user property has a value of N, then the sequence number of a new or copied record is generated as the seque

equence number generated is based upon the current record position or the maximum sequence number.

a sequence field for which new and copied records are assigned a the maximum of the existing sequence values + 1, you would have to a

ness component requires several tasks to be completed. For detailed information on creating sequence fields, see Configuring Siebel Busi

ed field with no calculation and with this user property and Encrypt Source Field user property as child objects. Enter a value of 99999999

rent field a required field under certain conditions.

expression.

ated expression for the value of the user property. When the expression evaluates to Y, the field is required.

he text length of the field, rather than that of the database column, defines the maximum field length.

roperty is either TRUE or FALSE.

ext Length property of the field determines the maximum field length. If this user property is not defined, the size of the database column

ser property in older versions of Siebel applications.

record is generated as the sequence number of the current record + 1. Other records are renumbered, if necessary.

ce values + 1, you would have to add the following user properties to the business component:

fields, see Configuring Siebel Business Applications.

bjects. Enter a value of 999999999999999999 into the CC stored field and xxxxxxxxxxxxxx9999 appears.

d, the size of the database column determines the maximum field length. Use only for Text type fields.

if necessary.

I want to discuss an excellent use of BC user property which lent me a hand to achieve a tricky requirement. The business re Finally what came to our rescue was the Aspect BC ReadOnly BC user property. This User Property works with CSSBCBase class. Steps to configure the requirement:

1. Create a Calculated field lets say Calculated Read Only in the respective BC (BC on which the applet is based).The calcul

2. Create a new record in the Business Component User properties with Name Aspect BC ReadOnly: ReadOnly Value Calculated Read Only *Name of the calculated field created above+

3. Create a New record in the Applet User Properties of the respective Applet Name View Aspect: Account Detail Orders View [Name of the view in which this applet should appear Read Only] Value ReadOnly *This refers to the variable given against the Name of the BC User Property above marked in Bold+

4. Now login to the application and see that in the view mentioned the applet appears to be read only while in other view it As can be seen here, in the Account Detail Contacts View the Applet SIS Account Entry Applet appears editable.

While the same applet SIS Account Entry Applet is entirely Read only in the Account detail Orders View

If you have any better ideas to achieve this, suggestions are most welcome

cky requirement. The business requirement was to use one applet in two different views. In first view that applet should appear editable

ich the applet is based).The calculated field expression should be such that it always returns value as Y, like one can create an expressio

t should appear Read Only] rty above marked in Bold+

e read only while in other view it is well editable

plet appears editable.

Orders View

that applet should appear editable while in other it should be Read only. Business did not want to go for cloning the applet as it turns out

, like one can create an expression as IIf (*Id+ IS NULL,N,Y), so that it returns Y for every record available.

cloning the applet as it turns out in making same changes in two different applets and might end up in missing out some changes in eith

missing out some changes in either applet. Also the number of fields on the applet was large hence we did not give it a thought of using

did not give it a thought of using FieldReadOnly user property in some way.

Parent Read Only Field

This user property allows you to specify a TRUE/FALSE (Y/N) test on a business component/field comb

Value

The value for the Parent Read Only Field user property consists of a pair of period-separated parameters, as follow buscompname .fieldname

buscompname specifies the name of the parent business component, and fieldname specifies the name of the fie

Usage

When the value of the specified field evaluates to TRUE or Y, the current business component becomes read-only

The business component to be conditionally restricted is the one to which you add the user property as a child ob

Parent Read Only Field is used primarily to restrict the detail records in a multi-value group. It could also be used t

NOTE: When using the Parent Read Only Field user property, the test field must have its Link Specification prop

Parent Read Only Field: buscompname

Value Usage

The value for the Parent Read Only Field: buscompname user property specifies the name of the field The behavior of this user property is similar to that of Parent Read Only Field, but its name, rather tha

When the calculated value of the specified field evaluates to TRUE or Y, the child business component

This user property allows a child business component to have TRUE/FALSE tests on multiple parent bu Parent Read Only Field: Incentive Compensation Component Parent Read Only Field: Incentive Compensation Hurdle Parent Read Only Field: Incentive Compensation Personal Plan Component Parent Read Only Field: Incentive Compensation Personal Hurdle Parent Read Only Field: Incentive Compensation Plan Component Parent Read Only Field: Incentive Compensation Plan Hurdle Parent Read Only Field: Incentive Compensation Plan Rule Individualized The value of the user property in each case is Filters RO Flg, a calculated field

Parent BC: Service Request Child BC: Activities If Service Request business component Status field is closed then the Action BC should become read only.

1. Create a Calculated Field in Parent BC Service Request as shown below Field Name: Calc Status Closed Calculated Value: IIF([Status] = Closed,Y,N). Thanks Vijaya for noticing it Note: Set the Links Specification Property to TRUE for the field: [Calc Status Closed] 2. Create a BC User Property in Child BC Action as shown below Name: Parent Read Only Field: Service Request Value: Calc Status Closed And it is done

a business component/field combination in the parent business component that, when TRUE or Y, causes the child business component to

d-separated parameters, as follows:

name specifies the name of the field in the parent business component.

ss component becomes read-only.

dd the user property as a child object definition. The business component containing the test field must be a parent or grandparent of the

alue group. It could also be used to restrict the detail records in a master/detail view, but in that case you need to make sure that the res

st have its Link Specification property set to TRUE. Otherwise, the dynamic read-only functionality does not work. However, if the child

rty specifies the name of the field in the parent business component that has a calculated value that evaluates to TRUE or FALSE (Y or N). nly Field, but its name, rather than its value, specifies the parent business component.

r Y, the child business component becomes read-only.

FALSE tests on multiple parent business components. For example, the Incentive Compensation Filter business component has seven of th

BC should become read only.

es the child business component to become read-only.C29

be a parent or grandparent of the restricted business component by way of a link or series of link relationships.

ou need to make sure that the restricted business component is not also used in the context of some other business object than the inten

es not work. However, if the child record is displayed in the multi-value field in the parent business component, it is not necessary to hav

luates to TRUE or FALSE (Y or N).

usiness component has seven of these user properties:

her business object than the intended one.

ponent, it is not necessary to have the Link Specification property of the field set to TRUE.