Persistent Property Explanation : A persistent property retains its value in the sense that its value is saved in the Teamcenter database and is not lost even if the Teamcenter server is shut down or restarted. When the server is restarted, the values of persistent properties are reloaded from the database and are available for use in the system.
For example, let's consider a custom business object "Product" that has a persistent property "Product Name". If a user creates a new Product object and sets its Product Name to "Widget X", this value will be saved in the Teamcenter database. Even if the Teamcenter server is shut down and restarted, the value of the Product Name property will still be "Widget X" when the user accesses the Product object again.
In contrast, if a property is not defined as persistent, its value will be lost when the Teamcenter server is shut down or restarted. This type of property is commonly referred to as a "transient property". Transient properties are used to store temporary information that is needed only for a specific session or operation, and do not need to be saved in the database.
Compound Property : A "compound property" in BMIDE is a property that is composed of multiple sub-properties, also known as attributes. Compound properties are used to represent complex data structures, such as an address or a date-time value.
A compound property is a property on a business object that can be displayed as a property on another business object. A compound property creates the path that the property follows to display the source business object property on the target business object. For example, you can use a compound property to display a custom property from a form on a business object. A compound property uses Relation and Reference properties to traverse from the source to the destination object.
A compound property can be thought of as a container that holds multiple attributes, each of which can have its own data type, such as string, integer, or real. The sub-properties of a compound property can also be persistent or transient, and they can be used just like any other property in the system.
For example, consider a custom business object "Person" that has a compound property "Address". The Address property could be composed of several sub-properties, such as "Street", "City", "State", and "Zip Code". By using a compound property to represent an address, you can manage the address information as a single entity, rather than having to manage multiple properties for each individual attribute of the address. This makes it easier to create relationships between objects, perform data validation, and enforce business rules.
Runtime Property : Runtime properties are derived each time the property is displayed, their data is derived from one or more pieces of system information (date/time) That are not stored in TC database.
Relation Properties : Relation property are properties that define the relationship between object,
Eg: Dataset can be attached, to an item revision with specification, requirement or reference relation, among others.
Comments
Post a Comment