Properties & Terminologies
Understanding properties and terminologies is crucial for effective data categorization and operation within Uniscale. This section delineates their differences, attributes, and application scenarios
Last updated
Understanding properties and terminologies is crucial for effective data categorization and operation within Uniscale. This section delineates their differences, attributes, and application scenarios
Last updated
A property represents a data field that holds values defining characteristics of an object or entity within uniscale. In particular; , , and .
Property groups, as implied by their name, are collections of related properties bundled together. For example, while modeling an address, one might combine properties such as street address, city, and country into a single "address property group." This approach simplifies the organization of related properties.
Types of Properties:
We have three distinct types of properties; native properties, reference properties, and value object properties. Each of these types can be sub-categorised as below:
Native:
String: Contains text.
Boolean: Represents true or false.
Int: An integer number.
Float: A number that includes a decimal point.
Date: Represents date only.
DateTime: Combines date and time.
Guid: Globally unique identifier.
Terminology: Enum-like structure housing predefined data points. (see further breakdown below)
References: Point to other entities or objects.
Value Objects:
Create New (for company): Generates a value object accessible company-wide.
Create New (for product): Generates a product-specific value object.
Available Value Objects: Selection from pre-existing value objects
Cardinality:
Single: Property can hold only one value.
Multiple: Property can hold multiple values.
To create a property, start by creating a value object.
After creating a property, selecting it will open a context menu on the right side where you can adjust its property type and cardinalities as follows:
A terminology is a subtype of native properties. It is akin to an enumeration (enum) in programming, offering a predefined set of data points. This structure enables controlled vocabulary within fields where only specified values are permitted, ensuring data integrity and consistency.
Given an example of a phone number, we can have a terminology property for "Type"
we can add two possible values for this terminology, "Home" and "Work" meaning when this property is used, it can only take on the values of either "work" or "home"
