Concepts : Concept Resource Reference

Concept Resource Reference
Concept resources are descriptive entities similar to the object-oriented concept of a class. They describe a set of properties. For example, one concept might be Department, and it could include department name, manager, and employee properties.
If you are working with a project imported from a release earlier than 5.0.0, you may see metadata properties. However, do not use them. Instead use the settings and properties in the Domain Objects section of the CDD file as needed. See TIBCO BusinessEvents Administration for details.
Wizard and Configuration Tab
The Wizard and Configuration tab have the following fields.
The name to appear as the label for the resource. Names follow Java variable naming restrictions. Do not use any reserved words. Names must be unique within a folder. See Identifiers (Names).
This field appears on the New Concept Wizard. The name then appears in the title of the concept editor.
Concepts that are related to each other directly or indirectly by inheritance cannot have distinct properties that share a common name. Therefore the following restrictions apply:
If two concepts are related by inheritance, you cannot create a new property in one with a name that is already used in the other.
If two unrelated concepts have properties that share a name, an inheritance relationship cannot exist between them.
The function has a parameter specifying whether child concepts’ state machines are also started. For contained concepts, the value of the Auto Start State Machine is not relevant and is not checked.
Properties
The Properties tab has the following fields:
String, Integer, Long, Double, Boolean, DateTime, ContainedConcept, ConceptReference
When you create a property of type ContainedConcept, you are creating a containment relationship. The concept that you are currently configuring is the container; the concept you specify as a property is the contained concept.
When you create a property of type ConceptReference you are creating a property that references another concept.
See Concept Relationships in TIBCO BusinessEvents Architect’s Guide for more details.
Note: For properties of type Double, when a backing store is used, all NaN (Not a Number) values are converted to 0.00.
Consider, for example, an Order concept: In most cases, an Order concept would allow only one value for the customer property but multiple values for the line_item property. Selecting the Multiple checkbox creates a property array.
Changes Only TIBCO BusinessEvents records the value of the property every time it changes to a new value.
All Values TIBCO BusinessEvents records the value of the property every time an action sets the value even if the new value is the same as the old value.
The default maximum value is 1024. You can set a different maximum using the property The maximum value allowed is 1024.
Zero (0): TIBCO BusinessEvents does not store historical values for the concept. It stores the value without a time and date stamp
One or more (>0): TIBCO BusinessEvents stores the property value when the property changes, along with a date and timestamp, up to the number specified. When the maximum history size is reached, the oldest values are discarded as new values are recorded. See Concept Property History in TIBCO BusinessEvents Architect’s Guide for more details.
Note: Use of a temporal function with a concept that has a history size of 0 may cause a runtime exception.
Metadata
The Metadata section is used in a special way with database concepts. Requires TIBCO BusinessEvents Data Modeling. See TIBCO BusinessEvents Data Modeling Developer’s Guide for details. It is not used otherwise (except for customization, which is not documented).