|
| 1 | +--- |
| 2 | +author: meshcloud |
| 3 | +title: Release 2025.37.0 |
| 4 | +--- |
| 5 | + |
| 6 | +Release period: 2025-08-21 to 2025-08-27 |
| 7 | + |
| 8 | +This release includes the following issues: |
| 9 | +* Fix Import Issues for Building Block Definitions From meshHub |
| 10 | +* Warning for Problematic Markdown in Building Block Input Description |
| 11 | +* Improved Documentation for meshWorkspace Tags API |
| 12 | +* Quickly view a Project's Tenants in the Admin Area |
| 13 | +<!--truncate--> |
| 14 | + |
| 15 | +## Ticket Details |
| 16 | +### Fix Import Issues for Building Block Definitions From meshHub |
| 17 | +**Audience:** User<br> |
| 18 | + |
| 19 | +#### Description |
| 20 | +Fixed several issues when importing building block definitions from meshHub. The system now properly validates and |
| 21 | +converts input types (boolean, integer, select options) instead of silently ignoring invalid data. Boolean default |
| 22 | +values are now correctly displayed in the panel. |
| 23 | + |
| 24 | +#### How to use |
| 25 | +When importing building block definitions from meshHub, the system will now provide clear error messages if the |
| 26 | +imported data contains invalid type conversions (e.g., non-boolean values for boolean inputs). |
| 27 | +If you already imported a building block definition and observed problems when trying to create building blocks |
| 28 | +from it, you can try the following: create a new draft from your building block definition, edit and save the |
| 29 | +problematic inputs and then release the new version. This will fix the incorrect default values. |
| 30 | + |
| 31 | +### Warning for Problematic Markdown in Building Block Input Description |
| 32 | +**Audience:** User<br> |
| 33 | + |
| 34 | +#### Description |
| 35 | +We added a warning that appears when you enter potentially problematic characters in building block definition |
| 36 | +input descriptions. The warning helps prevent markdown rendering issues by alerting you when characters like '<' or '>' |
| 37 | +are used without proper escaping. |
| 38 | + |
| 39 | +### Improved Documentation for meshWorkspace Tags API |
| 40 | +**Audience:** User<br> |
| 41 | + |
| 42 | +#### Description |
| 43 | +We improved the documentation for the meshWorkspace API to clarify tag handling. The documentation now explicitly states |
| 44 | +that you must always provide a tag object with all the tags you want to have on the workspace (you can fetch previously |
| 45 | +existing tags for example via the GET endpoint). It can be an empty object, if you want to remove all tags or don't use any |
| 46 | +workspace tags anyways. |
| 47 | +Additionally, we clarified which fields are read-only after creation. |
| 48 | + |
| 49 | +### Quickly view a Project's Tenants in the Admin Area |
| 50 | +**Audience:** Partner<br> |
| 51 | + |
| 52 | +#### Description |
| 53 | +We have added a new action on the admin area project list to quickly view tenants |
| 54 | +of this project. The link opens up the tenant list pre-filtered on the |
| 55 | +selected project. |
| 56 | + |
0 commit comments