/
Release CW 48/2025

Release CW 48/2025

Release date: Nov 26, 2025

New Features

Remote Access: Internal and Shared Endpoint Configurations

OperatorService Provider

Machine owners can define Remote Access endpoints as Internal (only for their own tenant) or Shared (usable for all linked tenants).

All existing endpoints were migrated to Shared endpoints.

Operator View

  • Operators see all endpoints (Internal and Shared).

  • Service Provider Internal endpoints are shown greyed out when the Service Provider marks the endpoint as internal.

Service Provider View

  • The Service Provider can see their own Internal endpoints and all Shared endpoints.

  • Operators´ internal endpoints remain hidden.

Additional

  • Clear labeling of Internal/Shared in all views.

  • Endpoints will be removed when machine ownership or linked tenants are changed.

 

OS Update: Hint for Required Intermediate Version

OperatorService Provider

When updating an Edge Device OS, the portal now shows a hint if an intermediate OS version must be installed before updating to the latest release.

Changes, Improvements, and Fixes

Comments and Deprecations in Public API Documentation

OperatorService Provider

Fields that are deprecated in the symmedia Hub schema are now highlighted in the API documentation for easier identification and substitution.
Please be aware that deprecated fields will remain in the API for at least 12 months after deprecation but will be removed afterwards.

https://symmedia.atlassian.net/wiki/spaces/SSH/pages/17334009888

 

Changes to the Public API for the Customer Machine and Asset Objects

The Machine Object has been added as a federated field to Customer Machines and Assets, allowing you to query additional fields (e.g., warranty and collaboration status) and substitute some field of these objects. Please check the API documentation for details:
https://symmedia.atlassian.net/wiki/spaces/SSH/pages/17334009888

 

Restricting Recursion Depth for All GraphQL Calls

In the public API, the maximum recursion depth is eight to prevent DOS attacks. This should not affect existing API implementations. However, if this recursion depth is insufficient for your use cases, please contact our support team.