Marie-Joy Hodel

It would be very helpful, when there is a possibility to export a PDF file from the entity service case.

When creating an appointment, an invitation is usually sent directly to the customer as soon as an email is stored. However, there are exceptions where invitations should not be sent.

If an appointment has already taken place, you should still record the appointment but without sending an invitation.

For example, it would be nice to work with a button.

Button = Send Invitation

If it is set to No, the appointment should not send an invitation to the customer. If so, the appointment can be sent to the customer.

Currently, sharing links within the same environment and database creates unnecessary friction in daily collaboration. Even when all users involved are part of the same team and have identical access rights, they often cannot open shared links directly if these are tied to a specific App ID or app context.

This is particularly problematic in collaborative workflows, where link sharing is intended to simplify communication and speed up processes. Instead, it introduces confusion and additional steps, as colleagues are unable to reliably open shared record, even though they are already authorised and working in the same environment.

From a security perspective, this limitation does not seem necessary. Access is already properly controlled through existing role- and permission-based security mechanisms. If a user does not have access to a record, the system correctly prevents it. However, if a user does have the required permissions, the link should open seamlessly regardless of the originating app or App ID.

A more flexible and user-friendly approach would therefore make much more sense:

• Allow app-independent record links without embedding a fixed App ID
• Or automatically redirect users to the correct app based on their permissions
• Or provide a universal link format that dynamically resolves the correct context for each user

This would significantly improve usability and collaboration within teams, reduce unnecessary friction in daily workflows, and increase the practical value of the sharing functionality, while fully maintaining the existing security model.