BiZZdesign release news – vol. 4
Audience: BiZZdesign user
In today's continuation of a series of articles about news in BiZZdesign, we will look at some interesting improvements. However, I must mention that I am looking forward to presenting you with the awesome news and functionalities contained in the BiZZdesign roadmap. I firmly believe that they will come out soon.
The latest version of BiZZdesign is marked as version 4 and its last release was released on June 07, 2021. Cloud solutions are upgraded automatically after the release. However, on-premise solutions are updated by customers at their own discretion. A quick and up-to-date description of the news can be found at the following link: Latest release. Latest release.
News of version 4 from June 07, 2021
- Relocation Principles view
- Selected default attributes marked deprecated
- Markdown available for text fields in Data Blocks
- Direct navigation between DMN decision tables in HoriZZon
- Layout configuration for automatic layout of concepts at view
- Data Policies also available for views and diagrams
1. Relocation Principles view
Principles view has moved to another position within the menu, currently located in ArchiMate > Motivation (menu for creating new views in Model Browser). The previous location was menu ArchiMate > Implementation and Migration.
2. Selected default attributes marked deprecated
Some of the basic attributes for ArchiMate objects have been marked as deprecated and will no longer be available. Specifically, these are the attributes:
- relatedGoals
- relatedPrinciples
- relatedGuidelines
- related_deliverables
- related_programs
- objrepl (replication)
- objrepls (replication number)
Within the objects Goal, Principle and Guideline the following attributes have been marked as deprecated:
- relSource
- relOwner
- relStatus
If you have used any of the above attributes, contact digitWin supportto help you migrate to other attributes.
3. Markdown available for text fields in Data Blocks
Data Blocks in HoriZZon also support the new text data type. This data type supports editing in the Markdown format, while the data type can be defined in the Data Block definition and then worked with in the HoriZZon portal.
4. Direct navigation between DMN decision tables in HoriZZon
In the HoriZZon portal, it is possible to navigate from the Decision concept in the Decision model view directly to the corresponding Decision table by clicking on the Decision table icon in the concept.
5. Layout configuration for automatic layout of concepts at view
Usually when using the Hierarchical layout feature on the ArchiMate view, the layout is from top to bottom. After the new one, it is possible to use another of the main layout methods via the Tagged value setting via the script below. The last argument in the setTaggedValue method indicates the direction of the layout, with possible values being:
- TB (default): Top to bottom
- LR: Left to right
- RL: Right to left
- BT: Bottom to top
view = selection[1];
view.setTaggedValue("fullLayoutDirection", "LR");See the online documentation for more information: Configuring the layout direction for the automatic layout of ArchiMate views.
6. Data Policies also available for views and diagrams
After the new one, Data Policies and Data Entry can also be used for views and diagrams. If a Data Block is mapped to a view or diagram within the Data Block definition, this Data Block will be available in the HoriZZon portal for all views or diagrams of the same type.
Selection of removed bugs in version 4 from 4 from June 07, 2021
TP-10709 – BPMN
When setting the cycle for call activity in BPMN and also when setting the called element, the controls for both settings are placed one above the other, which makes the object information invisible to the user.
TP-11907 – Enterprise analytics
The chart may have become corrupted after deleting the metrics used in the chart.
TP-11953 – Enterprise analytics
The matrix chart was not always created correctly in the HoriZZon portal, while the contents of the cells were shifted horizontally or vertically, thus covering other parts of the chart.
TP-11989 – Metamodeler
An error message is displayed when adding a value to a custom attribute of an ArchiMate object that references an object of the same type (such as a related Business Function).
TP-11239 – Modeling
Generating a view using Lay out afterward option caused a layout error.
TP-10862 – Scripting
In cases where the method removedTaggedValue was called in the script removedTaggedValue with more than 2 arguments, Enterprise Studio crashed.
TP-11936 – Scripting
Method findObject did not always find the object in the model package, even though the object existed.
TP-11835, TP-11974 – Team Platform
In some cases, the Administrator could perform a reflected XSS.
TP-10911 – Enterprise analytics
Table charts cells containing multiple text rows (such as documentation) did not display correctly in HoriZZon, text rows overlapped. Here's how to restore such charts:
- In Enterprise Studio, select the table chart that contains the overlapping text, and then click Reset size at the edge of the chart. Do this for each affected table chart in your model.
- Commit the changes and check them in the HoriZZon portal.