Application Data Areas
- Last UpdatedFeb 19, 2025
- 2 minute read
Application Data Areas and Elements are a new form of definition in the Design Database that are provided to assist Appware Applications to store model parts for copying and propagation within a design. They have some similarities with Templates, but are more general in content, and more restrictive in behaviour.
Application Data Areas and Elements are expected to be used for Piping Assemblies and Platforms Stairs and Ladders (PSL) applications and perhaps others. They are also expected to be used for storing Supports definitions to make the management of these more robust.
The Elements available are administrative elements allowing applications to organize data storage areas of design objects that are not part of the design itself, but supplementary objects used to create and maintain the model. They will not be accessed (unless specifically instructed to do so) when performing model queries such as clashing, mass properties, collections etc. They are similar to Catalog definitions and to Template definitions in particular.
The top level element in the Model database is Design WORL. This owns a top level application data element
|
APPLDWorld |
- Application Data World |
|
|
APPLDW can own |
||
|
APPDAReas |
- Application Data Areas |
|
|
DDAR |
- Design Data Set Areas |
|
DDARs are existing element types. They own Design Data Sets (DDSE) for storage of data used by Template expressions and Rules, and by Appware. They can be used for Appware to store data, rules, etc for use in data driven instancing of assemblies.
|
APPDAR can own: |
||
|
APPLDAta - Application Data. This is logically similar to a Template Definition. |
||
|
APPLDA is a new element type. It can own |
||
|
ZONE |
||
|
DDSE |
- Design Dataset |
|
|
DPSE |
- Design Pointset |
|
|
ROOM |
||
The following diagram illustrates the relative positions of these elements in the Model database hierarchy:
