New Features

Asset Creation for Operators

Operator

Workshop Managers are now able to create assets for all their machines on the shop floor even if the Service Provider is not (yet) on the platform. The assets can be used for internal Service Case Management and it is possible to uploads documents and media.

Furthermore, it is now possible to to purchase and pair Edge Devices with these created assets. With paired Edge Devices, Connected Services like Remote Access, SSC Data Link Tunnel or File Transfer can be used in the context of an internal Service Case.

Created assets are licensed according to the signed SaaS agreement that can be reviewed by Tenant Admins in the “Settings” → “Company” Tab.

Assets can only be actively used on the platform if billing information is shared with the platform operator and stored.

Check out the documentation at https://symmedia.atlassian.net/wiki/x/sgC9BgQ or get in touch with us at https://symmedia.atlassian.net/servicedesk/customer/portal/1/group/1/create/15 .

Enable Creation of shared Service Cases by Service Providers

Service ProviderOperator

Service Providers - namely users bearing the 1st Level Support and Service Technician are now able to create shared Service Cases for their already onboarded Customers. This is especially helpful if the Operator is temporarily unable to create the Service Case himself but needs assistance anyways.

Both the “Customers” (Operators) and the relevant users on the Service Provider side receive notifications upon Service Case creation.

Moreover, Operators have the possibility to disable the functionality for their tenant so that no Service Provider is able to create shared Service Cases for their Assets.

Applications can now be marked as “public”

Application ProviderOperator

It is now possible for Application Providers to mark applications as public. Public applications can be installed by all Operators who have not received their Edge Device from their Service Provider. Service Providers providing Edge Devices to their customers are still able to manage application availability by marking them as compatible.

Changes, Improvements, and Fixes

Introducing symmedia Hub

With this release the platform is rebranded to symmedia Hub. In the first step the notification Emails are rebranded as well as the default appearance and the default Logos. For more information see:

https://youtu.be/ZNuMwHBWrX0?feature=shared

Improved User Interfaces and Workflows for accepting Asset Proposals and editing Assets

Operator

According to the above mentioned “Create Asset” workflow, the workflows for accepting asset proposals and editing asset have been adopted.

The user interfaces are now more intuitive and easier to use and additional values such as model, brand and technology of the asset can be entered and edited.

Moreover, it is now possible to upload the asset image via drag & drop.

Facility is now an optional Field for Assets

https://symmedia.atlassian.net/wiki/spaces/SSHDS/pages/edit-v2/17697603585#Facility-is-now-an-optional-field-for-assets

Assets can now be created and edited without assigning a facility. This also applies if assets are created based on an asset proposal. Also, facilities can be created directly out of the create&edit workflows by just entering the name of the facility that should be created.

Improved Performance of Notifications in the Portal

OperatorService Provider

The performance of the notification backend has been improved for all users. Furthermore, the mechanism for marking notifications as read has been improved in the frontend.

Extended Functionality for WebVNC View