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.
Configuration
Field | Global Var? | Description |
---|---|---|
Name | No | 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. This field appears on the New Concept Wizard. The name then appears in the title of the concept editor. |
Description | No | Short description of the resource.
This field appears on both the New Concept Wizard and in the concept editor. |
Inherits From | No | If you want this concept to inherit all the properties of another concept, browse to and select that concept.
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:
|
State Models | No | State models that are owned by this concept. Models can be added and removed as needed.
Requires TIBCO BusinessEvents Data Modeling. |
Auto Start State Model | No | If selected, when a concept is asserted at runtime, its main state machine (if any) is started.
If not selected, then state machines are started using this function in rules: Instance.startStateMachine() 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 selected. Requires TIBCO BusinessEvents Data Modeling. |
Properties
Field | Global Var? | Description |
---|---|---|
Name | No | The property name.
Note: The property name cannot begin with the character
_ .
|
Type | No | Any of the following types:
When you create a property of type
Note: A concept cannot contain itself. For instance, for a concept A, we cannot add a contained property of type A.
When you create a property of type
See TIBCO BusinessEvents Architect’s Guide for more details. For properties of type Double, when a backing store is used, all NaN (Not a Number) values are converted to
|
Multiple | No | Select the Multiple check box if this property is an array.
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
|
Policy | No | TIBCO BusinessEvents can record historical values using either of these policies:
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.
|
History | No | Determines if historical values are stored, and if so how many.
The default maximum value is 32767. 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 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.
|
Domain | No | Domain associated with the property |