Model Import Options
There are two categories of import options for PHENOM: Import Checks/Fixes and Query Processing & Content Retention Options.
Import Checks/Fixes
Assert IDs
| Property | Value |
|---|---|
| Option | Assert IDs
|
| Default | Checked
|
| Allowed values | Checked-Unchecked |
Summary: Ensures that each imported entity has an identifier.
Details: The FACE Technical Standard requires every entity & association to have an identifier attribute to be a "valid" model. When enabled, this option ensures the identifier is added to the model as needed to satisfy the identifier requirement. NOTE: If an entity/association is a specialization, the identifier may not exist in the entity itself, but it must exist somewhere in the inheritance chain.
Fix paths not ending in Observable
| Property | Value |
|---|---|
| Option | Fix paths not ending in Observable
|
| Default | Checked
|
| Allowed values | Checked / Unchecked |
Summary: If a path ends in an entity or association, this will find an attribute in the entity and terminate on that instead.
Details: Although allowed by the FACE Technical Standard, pointing to an entire entity (or association) limits model extensibility. This import option fixes your model by moving that endpoint from the entity to an attribute.
Fix View Characteristics w/o name
| Property | Value |
|---|---|
| Option | Fix paths not ending in Observable
|
| Default | Checked
|
| Allowed values | Checked / Unchecked |
Summary: Ensures that each view characteristic has a name. When a name is not specified, it is taken from the corresponding platform attribute.
Details: The FACE Technical Standard allows the name to be omitted from a view attribute. When this is done and a name is needed (e.g., during data type generation), the names are used from the corresponding attribute in the entity model. This option makes the names explicit at the time of import.
Detect and reuse existing Shared Data Model
| Property | Value |
|---|---|
| Option | Detect and reuse existing Shared Data Model
|
| Default | Checked
|
| Allowed values | Checked / Unchecked |
Summary: Detects the SDM used by the model and adds it as a separate model.
Details: PHENOM manages a complete library of FACE Shared Data Models and is able to detect when a model uses of these SDMs. This option makes the SDM a separate model within the project so it can be updated and changed over time.
Unbounded CDM Mode (Default Checked)
PHENOM best practices recommend bounds that differ from the standard-defined .face bounds. This option will apply the PHENOM-recommended bounds - (1..*) for all composed attributes/participants and (0..*) for all participant source roles.
Query Processing & Content Retention Options
Process CDM Queries (Default not Checked)
Process the Conceptual Queries. This will used specified observables and create generic logical and platform elements in the model with "placeholders" where logical and platform type would otherwise be specified.
Process LDM Queries (Default not Checked)
Process the Logical Queries. This will use the specified logical types and create generic platform elements in the model with "placeholders" where platform type would otherwise be specified.
Retain Queries (Default not Checked)
This will retain all platform queries. Upon export, if these queries remains unchanged, they will be exported "as-is." When not enabled, exported queries may look slightly different (but will retain the same semantic).
Retain Entity Models (Default not Checked)
This will retain all Logical and Platform Entities (and Associations). This is useful when strict tracking of these elements' GUID is desired.
Retain Auto Generated Content (Default not Checked)
This feature preserves any automatically generated content PHENOM may have added during export. NOTE: PHENOM only does this to ensure model validity.
Apply Explicit Default Values (Default Checked)
Ensures default values are made explicit in the model (instead of relying on implied default values).