Siebel Developer's Reference > User Properties > Overview of User Properties >

Numbering Instances of a User Property

Siebel CRM can use some user properties on multiple instances of a single business component or applet. If more than one instance of this user property exists, then Siebel CRM runs each instance sequentially. It uses Name n, such as On Field Update Invoke 1, On Field Update Invoke 2, and so on to identify multiple instances of a user property. In most situations, if the business component or applet includes only one instance of the user property, then Siebel CRM does not require this number.

Example of Numbering Instances of a User Property

For example, the Asset Mgmt - Asset (Order Mgmt) business component includes the following user properties:

On Field Update Invoke   "Product Name", "Asset Mgmt - Asset", "CopyXA"
On Field Update Invoke 1   "Product Name", "Asset Mgmt - Asset", "GeneratePartNumber"
On Field Update Invoke 2   "Product Name", "Asset Mgmt - Asset", "SaveCxProd"
On Field Update Invoke 3   "Quantity", "Asset Mgmt - Asset", "SetExtendedQuantity"

If Siebel CRM updates the Product Name field in the Asset Mgmt - Asset (Order Mgmt) business component, then it calls the following methods that the Asset Mgmt - Asset business component uses:

• CopyXA
• GeneratePartNumber
• SaveCxProd

If Siebel CRM updates the Quantity field in the Asset Mgmt - Asset (Order Mgmt) business component, then it calls the SetExtendedQuantity method that resides in the Asset Mgmt - Asset business component.

If you do not specify FieldToCheck, then Siebel CRM calls the CopyXA method in the Asset Mgmt - Asset business component when the user saves the record. For example:

On Field Update Invoke "", "Asset Mgmt - Asset", "CopyXA"

Guidelines for Numbering Instances of a User Property

If you configure Siebel CRM to create multiple instances of a user property, then it is recommended that you use the following guidelines:

• Number each instance.
• Use consecutive numbers. For example, use Deep Copy 8, and then Deep Copy 9.
• Do not include a gap between a number that is greater than 9.
• Do not append a number that includes more than two digits.

The following examples create unwanted results:

• You use On Field Update Invoke 10 but no instances exist that use numbers less than 10.
• You use Deep Copy 9 and Deep Copy 19 but no instances exist that are numbered sequentially between 9 and 19.
• You use Named Method 100.

For more information, see How This Book Describes the User Property Format.