Bookshelf v7.7: About Business Rule Process Property Types

Properties can be categorized into two classes—Simple and Complex. Simple property types are scalar properties such as an integer, string, or date. Complex property types are non-scalar properties such as property sets, vectors, and Siebel Business Component references.

At run time, values for global properties can be passed in as an input argument to the BRP business service. This run-time value overwrites the initial value definition if any on the property.

TIP: Use an appropriate prefix, such as global_, local_, or l_ to designate local and global properties.

Table 16. Complex Property Types
Type	Description
BusComp	This data type stores a reference to a Siebel Business Component (BC) and is used in conjunction with the FINS CAP Buscomp Handler business service. See Using BRP Helper Business Services. BusComp is used within BRP process as a stand-alone BC without the context of Business Object (BO). Hence, the BusComp has to be explicitly queried with the correct key values to establish a context.
Property Set	Property sets are collections of properties which can be used for storing data. They may have child property sets assigned to them to form a hierarchical data structure. See Siebel Object Interfaces Reference. Property Set itself can contain child property sets. This is particular convenient to store array-like data. For example, to store multiple contacts and their properties such as Name, Phone Number, and Date of Birth, each contact is stored as a child property set of Contacts. At the leaf, the property map stores data as a name-value pair. A property set cannot be instantiated with an assignment. Property sets are always instantiated using a business service, such as FINS CAP Buscomp Data Loader Service. See Using BRP Helper Business Services.
Vector	Vectors are special-formatted Property Sets, where each non-leaf node stores a unique key as its value. NOTE: The vector root node type for a BRP process is always SEBLFACapVector. A vector cannot be instantiated with an assignment. Vectors are always instantiated using an business service, such as FINS CAP Buscomp Data Loader Service. See Using BRP Helper Business Services. The following diagram shows a ProductRate vector that has 2 levels - Region & Product name. At the leaf level the vector stores the rate and the balance as key value pairs.
Vector Reference	Vector Reference is a reference to a property set, vector or a child property set. Once defined, Vector Reference can be used as a vector or propertyset. When the referenced object is reset, the dependent reference is automatically set to NULL. This property set is particularly useful when accessing data on the child property sets. A child Property Set reference can be made in the following two ways: childPropertySetRef = parentPropertySet[strkeyValue] childPropertySetRef = parentPropertySet(nIndex) Round parentheses ( ) are used to retrieve a child Property Set by index. NOTE: The index starts at 0. Square parentheses [ ] are used to get a child Property Set by value. NOTE: Accessing by value is only valid for Vectors. Only literals or property names can be used within [ ] or ( ). Expressions cannot be used within. TIP: To use expressions within [ ] or ( ), assign these to a simple property type and use the simple property within [ ] or ( ). Square and round parentheses can be used in combination. Example: grandchildPropertySetRef = parentPropertySet(2)["California"] In the preceding notion, parentPropertySet itself can be a reference. In other words, a reference and a property set are used interchangeably for data access. To retrieve the leaf properties, use [ ]. Example: ProductRate = productRate[productId][domain]["Annual Fee"]