EntityDesigner Reference

 

Diagram

  • Domain: name of the Schema represented in the Diagram. It stands for the NameSpace of element classes in the code and can be nested into another Domain.
  • Allow DomainProvider: if true,DomainProvider is accessible from Domain Class; this is usefull when several Diagrams are on the same Domain. In this case, only one DomainProvider is allowed.

Entity

  • Name: logical Name of Entity.
  • Guid Identifier: if true, Entity identifier is automatically defined with a Guid member, named Id. If false, Entity should have a Property defined as Identifier.
  • Partial Class: if true, corresponding Entity Class is partial, allowing custom extension.
  • Persist: if true, Entity change is managed during load and save operation. Otherwise, Entity changes are ignored during load and save operation.
  • Physical Name: name of the corresponding physical table in the RDMS, used in queries.
  • Physical Schema: name of the corresponding physical schema in the RDMS, used in queries.
  • Custom Validators: use a specific Command which is called when Validation is set in DataBinding. This feature is only available with Aspectize Core Server (not available with Aspectize DAL Component).
  • Trigger Delete, Insert, Update: use a specific Command which is called each time an Entity is inserted, deleted or updated. This feature is only available with Aspectize Core Server (not available with Aspectize DAL Component).
  • Update History: manage automatic timestamp metadata of Entity. This feature is only available with Aspectize Core Server (not available with Aspectize DAL Component).

Relation

  • Name: logical Name of Relation.
  • Partial Class: if true, corresponding Relation Class is partial, allowing custom extension.
  • Persist: if true, Relation change is managed during load and save operation. Otherwise, Relation changes are ignored during load and save operation.
  • Physical Name: name of the corresponding physical table in the RDMS, used in queries.
  • Physical Schema: name of the corresponding physical schema in the RDMS, used in queries.
  • Separate Table: boolean attribute which indicates if Relation is stored in a Specific Table in the RDBMS. Otherwise, storage is done through an Entity Table foreign key. A Relation with cardinality N-N must be separate.
  • Custom Validators: use a specific Command which is called when Validation is set in DataBinding. This feature is only available with Aspectize Core Server (not available with Aspectize DAL Component).
  • Trigger Delete, Insert, Update: use a specific Command which is called each time an Relation is inserted, deleted or updated. This feature is only available with Aspectize Core Server (not available with Aspectize DAL Component).

Role

  • Role: name of the Role played by Entity in the Relation. By default, Role Name is the same as Entity Name. A Relation must have 2 different Roles. In a recursive Relation Role must be defined.
  • Cardinality: use to determine how an Entity contributes in the Relation. Cardinality can be one of the following values: [0-1], [1-1], [0-N], [1-N]. Cardinality is used to manage constraints in memory.
  • Container: boolean attribute to specify if Role has a container meaning for the underlying Entity. Container are used in several operations:
    • Deleting an Entity, will delete all related entities through a Container Role (also call deleting cascade)
    • Querying an Entity, will query related Entities through a Container Role, with the Full Query API.
  • FKNames: indicates the physical names of PK columns of Relation. Logical Name of Relation FK Columns is automatically set and cannot be changed. If FK is multiple, physical names should be separated with commas.
    • If Relation is Non-Separate, FKNames indicates the physical name of the parent Entity FK (Role [0-1] or [1-1]) in the child Entity Table.
    • If Relation is Separate Table, FKNames is the physical Name of the PK Entity in the Relation Table.

CompositeType

  • Name: logical name of the Composite Type

 

Property

  • Design
    • Default Value: indicates the value automatically filled in the property when a new Data is created. String default value should be quoted. DefaultValue Provider Command may be used with Aspectize Server.
    • Expression : used to create Calculated Columns in an Entity. The Expression can be a DataColumn Expression or a Command Expression (only available with Aspectize Server). Calculated Columns are read-only.
    • Identifier: used to define how the property participates in constraints; can be Unique or Identifier.
    • Multiplicity: used to define the multiple characteristic of the Property. By default, Multiplicity is Simple. If Type is a Composite Type, Multiplicity can be Multiple, Temporal (with 1 Date Property Identifier) or Periodic (with 2 Date Properties Identifier, Start and End).
    • Name: logical name of the Property.
    • Nullable: indicates whether null values are allowed in this property.
    • Type:  indicates type of data stored in the Property. Type may be simple Type (Boolean, Byte, ByteArray, Char, DateTime, Decimal, Double, Guid, Int16, Int32, Int64, SByte, Single, String, Text, UInt16, UInt32, UInt64) or CompositeType or Enum defined in the same Schema, or in an external Schema.
    • ExternalType: points to a Type of another external Schema. Type should include complete Namespace.
  • Persistence
    • FKNames: used in a Multiple Property to design the Physical Name of the PK Columns in the Multiple Table
    • Identity: indicates whether the Column is AutoIdentity. If true, new value is automatically set when new data is inserted in the RDMS.
    • MustPersist: if true, Property changes are managed during load and save operation. Otherwise, Property changes are ignored during load and save operation. This attribute is useful to add some calculated information to an Entity, with an expression or with code.
    • PhysicalName: name of the corresponding physical column in the RDMS, used in queries
    • Scale: scale of the column in the RDMS.
    • Size: defines the maximum length of a string data.
  • Validation
    • Custom Validators: used to automatically validate data with specific command through DataBinding. This feature is only available with Aspectize Core Server (not available with Aspectize DAL Component).
    • Min Value: used to define a minimum value of data through DataBinding. This feature is only available with Aspectize Core Server (not available with Aspectize DAL Component).
    • Max Value: used to define a maximum value of data through DataBinding. This feature is only available with Aspectize Core Server (not available with Aspectize DAL Component).
    • RegEx Pattern: used to define regular expression validation rule value of data through DataBinding. This feature is only available with Aspectize Core Server (not available with Aspectize DAL Component).
    • System Validator Message: string message to show when data is invalid. This feature is only available with Aspectize Core Server (not available with Aspectize DAL Component).
  • Extra UI Properties. These properties are used to make available some more expressions to DataBinding, without poluating schema minor UI information.
    • Back Color: string expression that can be databound to BackColor Property control.
    • Enabled: boolean expression that can be databound to Enabled Property Control.
    • Fore Color: string expression that can be databound to ForeColor Property control.
    • Format: string expression that can be databound to Format Property control.
    • Required: boolean expression that can be databound to Required Property Control.
    • Visible: boolean expression that can be databound to Visible Property Control.