|
| 1 | +--- |
| 2 | +author: meshcloud |
| 3 | +title: Release 2025.4.0 |
| 4 | +--- |
| 5 | + |
| 6 | +Release period: 2025-01-22 to 2025-01-29 |
| 7 | + |
| 8 | +This release includes the following issues: |
| 9 | +* Non Admin Users Can Not Modify Locations Anymore |
| 10 | +* Enhancements to Building Block Definition Creation |
| 11 | +* Revised access control search |
| 12 | +* Fix Boolean Building Block Inputs |
| 13 | +* Remove unassigned users from notification recipients |
| 14 | +* API key row alignment |
| 15 | +* Adding Access Request Rejected to Event Logs |
| 16 | +* Merge Building Block Menus into One |
| 17 | +* Fix SCIM Group Deletion |
| 18 | +* API Key read-only Permissions for Workspaces |
| 19 | +* Remove Project Deletion Queue |
| 20 | +<!--truncate--> |
| 21 | + |
| 22 | +## Ticket Details |
| 23 | +### Non Admin Users Can Not Modify Locations Anymore |
| 24 | +**Audience:** User<br> |
| 25 | + |
| 26 | +#### Description |
| 27 | +As locations are potentially shared between different platform instances the edit right for regular users |
| 28 | +was removed. Locations can now only be edited by admins from the admin area. |
| 29 | + |
| 30 | +### Enhancements to Building Block Definition Creation |
| 31 | +**Audience:** User<br> |
| 32 | + |
| 33 | +#### Description |
| 34 | +In this release, we enhanced the General tab of the Building Block Definition creation interface. And we added a new input field that |
| 35 | +allows you to select the type of building block. This marks an important step toward supporting workspace building blocks in the future. |
| 36 | +At this stage, you can select only tenant building blocks. |
| 37 | + |
| 38 | +### Revised access control search |
| 39 | +**Audience:** User<br> |
| 40 | + |
| 41 | +#### Description |
| 42 | +In recent weeks, we have added the ability to search for users/groups |
| 43 | +within the access control screens. This change may cause unexpected |
| 44 | +validation errors. The view has been revised and made more robust. |
| 45 | + |
| 46 | +### Fix Boolean Building Block Inputs |
| 47 | +**Audience:** Operator<br> |
| 48 | + |
| 49 | +#### Description |
| 50 | +When editing building block inputs of type boolean, the default |
| 51 | +value was displayed instead of the actual value in some cases. This is now fixed. |
| 52 | + |
| 53 | +### Remove unassigned users from notification recipients |
| 54 | +**Audience:** User, Customer, Partner, Operator<br> |
| 55 | + |
| 56 | +#### Description |
| 57 | +Previously, there were occurrences where users removed from a workspace were still |
| 58 | +receiving notifications. Now, users removed from a workspace are periodically cleaned up |
| 59 | +from the notification recipients list. This ensures that only users with access to a workspace |
| 60 | +are notified. |
| 61 | + |
| 62 | +### API key row alignment |
| 63 | +**Audience:** User<br> |
| 64 | + |
| 65 | +#### Description |
| 66 | +We have resolved the alignment of the API key overview rows within the workspace control |
| 67 | +plane. The offset within rows has been resolved. The columns now match the row values again. |
| 68 | + |
| 69 | +### Adding Access Request Rejected to Event Logs |
| 70 | +**Audience:** Customer<br> |
| 71 | + |
| 72 | +#### Description |
| 73 | +Previously when 4-eyes principle was enabled, in rare cases no events were written when an access request to a workspace was rejected. This issue has been resolved, and access request rejected events are now consistently logged. |
| 74 | + |
| 75 | +### Merge Building Block Menus into One |
| 76 | +**Audience:** User<br> |
| 77 | + |
| 78 | +#### Description |
| 79 | +For a long time there were two menu items in the Admin Area & Service Management Area for managing building blocks |
| 80 | +and their definitions. We now merged these two menus and pages into one. This should make it easier to find what |
| 81 | +you are looking for. |
| 82 | + |
| 83 | +### Fix SCIM Group Deletion |
| 84 | +**Audience:** Customer<br> |
| 85 | + |
| 86 | +#### Description |
| 87 | +Previously, when you attempted to delete a group via SCIM that is assigned to one or more workspaces, an error occurred, preventing the action from completing successfully. This issue has been fixed. |
| 88 | + |
| 89 | +### API Key read-only Permissions for Workspaces |
| 90 | +**Audience:** Partner, User<br> |
| 91 | + |
| 92 | +#### Description |
| 93 | +Users can now add a new permission to API Keys to read the workspace that owns the API key from meshObject API. |
| 94 | +Admins can add a new admin permissions to API Keys that grants access to list all workspaces. |
| 95 | + |
| 96 | +### Remove Project Deletion Queue |
| 97 | +**Audience:** User<br> |
| 98 | + |
| 99 | +#### Description |
| 100 | +We have removed the project deletion queue which could be found in the workspace overview under projects -> Deletion Queue. |
| 101 | +A while back we introduced visibility of projects that are awaiting deletion directly in the project overview. |
| 102 | +This made the deletion queue redundant and we have now removed it. |
| 103 | + |
0 commit comments