#dominoforever Product Ideas Forum

 

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Meeting update doe not respect Encrypt checkbox

In a scenario whereby a policy is set (intentional) to encrypt all mail, there is an impact on meeting and the use of traveler.

 

Given a wish to be able to uncheck the Encrypt checkbox on sending a meeting invite, it has been noticed that any meeting update will not respect the option that is selected in the checkbox at all.

 

Steps

Create meeting, policy auto-checks Encrypt checkbox, user deselects checkbox. No problem.

Chair creates meeting update, policy auto-checks Encrypt checkbox, user deselects checkbox = problem, the update is sent encrypted meaning the update has not respected the choice made in the UI.

 

Business Impact

Recipients viewing these invites are often using Traveler which does not decrypt calendar items. Additionally the Org would instruct users not to encrypt meeting due to many delegates managing calendars on behalf of invitees, although the chairs are able to follow this advice, it does not work due to above.

 

Currently tracked as SPR # MSTR6QWR5W - Meeting not being (un)encrypted when update sent with added/removed encryption

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Sep 6 2019
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    09 Sep 07:56

    If something does not work the way the UI is coded, is that really an idea, or a new feature? I would think that such a behavior is rather a bug - and in this case even a security whole as the encryption is not honoring the setting in the UI and must therefore be fixed ASAP.