|
| 1 | +--- |
| 2 | +author: meshcloud |
| 3 | +title: Release 2025.14.0 |
| 4 | +--- |
| 5 | + |
| 6 | +Release period: 2025-03-28 to 2025-04-02 |
| 7 | + |
| 8 | +This release includes the following issues: |
| 9 | +* No service configuration possible while creating a tenant |
| 10 | +* Fix selecting all for building block bulk operations |
| 11 | +* Improves Behavior for Draft Landing Zone Building Blocks |
| 12 | +* Show Only Open Communication Items |
| 13 | +* Distinguish between Different Communication Types |
| 14 | +* Hides Non-Published Building Blocks in Marketplace |
| 15 | +* Clearer error message when Terraform cannot be parsed |
| 16 | +* Improved Sorting for User Lookups |
| 17 | +* Improved filtering for meshBuildingBlocks API |
| 18 | +* Sorting of Communications by sent date |
| 19 | +* Searchable Global Groups |
| 20 | +* Added missing columns to the chargeback statement export |
| 21 | +<!--truncate--> |
| 22 | + |
| 23 | +## Ticket Details |
| 24 | +### No service configuration possible while creating a tenant |
| 25 | +**Audience:** User<br> |
| 26 | + |
| 27 | +#### Description |
| 28 | +This fixes a bug that could prevent the configuration of any service during tenant creation |
| 29 | +while a building block definition with a single version was pending approval for this platform. |
| 30 | + |
| 31 | +### Fix selecting all for building block bulk operations |
| 32 | +**Audience:** Partner, Customer<br> |
| 33 | + |
| 34 | +#### Description |
| 35 | +This fix addresses an issue where the "Select All" checkbox in the building block |
| 36 | +bulk operations did not function correctly. It did not consider the context it was |
| 37 | +in. So e.g. instead of only selecting all building blocks of the currently open building |
| 38 | +block definition, it considered all building blocks the user has access to. This |
| 39 | +is fixed now and only the intended building blocks are considered. |
| 40 | + |
| 41 | +### Improves Behavior for Draft Landing Zone Building Blocks |
| 42 | +**Audience:** User<br> |
| 43 | + |
| 44 | +#### Description |
| 45 | +When you added unreleased building blocks as mandatory or recommended on a landing zone and are a user of a |
| 46 | +owning workspace you can now create tenants with this landing zone via the panel without an error. |
| 47 | +Regular users outside of the owning workspace can continue to create tenants in this landing zone |
| 48 | +without the draft building block until it is in a released state. |
| 49 | + |
| 50 | +### Show Only Open Communication Items |
| 51 | +**Audience:** Customer<br> |
| 52 | + |
| 53 | +#### Description |
| 54 | +The number on the badge now shows only the open communications. |
| 55 | +This ensures users have a complete overview of important updates |
| 56 | +and information without needing to navigate elsewhere. |
| 57 | + |
| 58 | +### Distinguish between Different Communication Types |
| 59 | +**Audience:** Customer<br> |
| 60 | + |
| 61 | +#### Description |
| 62 | +The workspace area has been updated to distinguish between "Action Required" and "Notification" items. |
| 63 | + |
| 64 | +### Hides Non-Published Building Blocks in Marketplace |
| 65 | +**Audience:** User<br> |
| 66 | + |
| 67 | +#### Description |
| 68 | +In the "related" tab of the marketplace view users outside of the provider workspace |
| 69 | +could see (but not use) unpublished building blocks. Now you only see those building blocks |
| 70 | +if you are a user in the owning workspace of the definition. |
| 71 | + |
| 72 | +### Clearer error message when Terraform cannot be parsed |
| 73 | +**Audience:** Operator<br> |
| 74 | + |
| 75 | +#### Description |
| 76 | +When creating a Terraform building block definition, if the Terraform code cannot be parsed, |
| 77 | +an unclear error message would pop up. We have improved this error message and made it more clear |
| 78 | +that even though an error occurred, you can still continue the building block definition creation process. |
| 79 | + |
| 80 | +### Improved Sorting for User Lookups |
| 81 | +**Audience:** User<br> |
| 82 | + |
| 83 | +#### Description |
| 84 | +We improved the relevance sorting when adding users or groups to your workspace. |
| 85 | +This should help to find the right user or group quicker. |
| 86 | + |
| 87 | +### Improved filtering for meshBuildingBlocks API |
| 88 | +**Audience:** Operator, User<br> |
| 89 | + |
| 90 | +#### Description |
| 91 | +We improved the filtering options for the meshBuildingBlock API v2-preview. |
| 92 | +The endpoint remains in preview mode for now. Future changes might still occur. |
| 93 | + |
| 94 | +### Sorting of Communications by sent date |
| 95 | +**Audience:** Partner<br> |
| 96 | + |
| 97 | +#### Description |
| 98 | +The communication list in the admin area now defaults to sorting by the "Send On" date, |
| 99 | +showing the most recent communications at the top. This change enhances usability by making |
| 100 | +recent items easier to find and reducing the need for manual sorting. |
| 101 | + |
| 102 | +### Searchable Global Groups |
| 103 | +**Audience:** Partner<br> |
| 104 | + |
| 105 | +#### Description |
| 106 | +We added a search field to the global groups overview in admin area. |
| 107 | +This allows you to search for global groups by name or identifier. |
| 108 | + |
| 109 | +### Added missing columns to the chargeback statement export |
| 110 | +**Audience:** Partner<br> |
| 111 | + |
| 112 | +#### Description |
| 113 | +To be compliant with the public API, we've added the two missing |
| 114 | +columns "baseCurrency" and "baseNetAmount" to the CSV export of |
| 115 | +the chargeback statement. |
| 116 | + |
0 commit comments