HoriZZon sites contain regular model information coming from metamodels and models in Enterprise Studio. The data is read-only and can be viewed and used for analysis goals, like in generated viewpoints, charts and dashboards.
In addition to the regular read-only information, HoriZZon supports model data enrichment with self-defined information. Sites can be enriched with data by defining sets of additional element attributes of which the values can be edited in HoriZZon. These sets of attributes are defined in data block definitions in Enterprise Studio. After being uploaded to the central data block store, the attribute values can be set and edited in data blocks in HoriZZon sites.
Data blocks can be used on diagrams, views, objects, and relations. The definitions are linked to their types. Different types of data can be entered in data block fields in HoriZZon, for example, money and date values, Boolean values, formatted text, and closed lists. Some of these field types can be calculated fields. Calculated fields are read-only, their value is automatically calculated based on values entered in other fields within the same data block.
To limit user edit rights for data blocks in HoriZZon, data policies can be set up. Maintenance of the data blocks can be arranged by defining data update schedules, which are part of the data policies. Scheduled maintenance is presented in data tasks that will be performed by users.
On this page:
Defining data block definitions
To enable working with data blocks in HoriZZon, data block definitions need to be defined in a shared model package in Enterprise Studio, and then uploaded to the data block store. The data block store is the central storage on the server containing all data block definitions created and uploaded by users. A data block definition consists of a set of attributes linked to one ore more diagrams, views, objects and/or relations.
Once a data block definition has been uploaded to the data block store, the associated data block is available in HoriZZon sites that are based on the model package in which the data block definition has been created. They are available in the diagrams, views, objects and/or relations of the types specified in the definition.
Setting up data policies
By default, data blocks are visible in sites that are based on the model package containing the data block definitions. They are located in their own section below the Properties section of the respective diagram, view, object or relation. Data blocks can be edited by all Contributor users. By setting up data policies you can limit data block editing for users and also set up data maintenance for the data blocks.
Data policies also enable Contributor users to edit data blocks on the data entry page of the model package without needing access to the site. Data policies can be set up at element level (diagram, view, object, relation), but also at data block level.
If you set up data policies at data block level, any other data blocks without data policies remain editable to Contributor users with access to the sites these blocks are in. You can even further limit these edit rights by setting a strict data block write access. With strict access, nobody can edit data blocks that do not have a data policy specified.
Setting up data maintenance
If you want data block values to be periodically updated by users, you add data update schedules to the data policies of the data blocks. The allowed editors of the data blocks will receive data task notifications for updating the values. Editors are directed from the data task to the data entry page with data blocks that need to be updated.
Editing data blocks in HoriZZon
Once data block definitions have been created in a model package in Enterprise Studio and uploaded to the data block store, the associated data blocks are available in shared HoriZZon sites based on that model package. Contributor users that have access to these sites can edit the data blocks. If data policies have been set up, these edit rights may be limited. With data policies, Contributor users can also edit data blocks via the data entry page of the model package.
Using data block values in Enterprise Studio
The values from the data blocks in HoriZZon can be used again in Enterprise Studio. You can use them for example in color views and charts, just like regular object attribute values. However, because data blocks and their values are stored separately from the model package information that is stored on HoriZZon, the data will be read-only in Enterprise Studio.
Automating data enrichment
Instead of or in addition to manually creating, updating and removing data block definitions and filling data block values in HoriZZon, the BiZZdesign Open API can be used for this. The API allows an authorized client application to directly create, modify and delete data block definitions in Enterprise Studio and to enter data block values in HoriZZon.
When you are including externally stored and managed data in your Enterprise Studio models using the Open API, you can even use data blocks to further enrich this data. Data blocks can be available for the entities in the collections of external data.