Bookshelf Home | Contents | Index | PDF |
Siebel Developer's Reference > User Properties > Overview of User Properties > Numbering Instances of a User PropertySiebel 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 PropertyFor example, the Asset Mgmt - Asset (Order Mgmt) business component includes the following user properties: On Field Update Invoke "Product Name", "Asset Mgmt - Asset", "CopyXA" 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: 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 PropertyIf you configure Siebel CRM to create multiple instances of a user property, then it is recommended that you use the following guidelines:
The following examples create unwanted results:
For more information, see How This Book Describes the User Property Format. |
Siebel Developer's Reference | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |