Skip to Main Content
HCL Domino Ideas Portal

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

Status No Plans to Implement
Workspace Verse
Categories Verse on Premises
Created by Guest
Created on Jun 12, 2019

Clicking on Discard button while email is in compose state should not move the email to Trash folder.

As per design, when we compose the new email it is auto saved, meaning it moves to Draft folder in the background.
When you click on the discard button it moves to trash folder as the email is autosaved already (which in turn moved to Draft folder).

In this default behavior if any email is in compose state when discarded it moves to Trash folder.

Expected result : Clicking on Discard button while email is in compose state should not move the email to Trash folder. In fact it should not move to any folder/views as well.

  • Attach files
  • Admin
    Timothy Clark
    Jan 23, 2024

    This is working ask designed. As the document has already been saved, deleting it will move it to the trash. As the trash gets auto cleaned on a regular basis, it will empty itself in the fulness of time.

    No Plans to implement.


  • Guest
    Jun 18, 2019


    The fact is that Discard button behaves in 2 ways: 

    1. if message has not been autosaved yet then the recent changes are discarded

    2. if message has been autosaved then the recent changes are autosaved AND then message is moved to trash ! Note: DISCARD = AUTOSAVE + move to Trash. User cannot DISCARD any further changes before next autosave if at least one autosave has happened. DISCARD will AUTOSAVE.

    I raised the support case for IBM / HCL that Discard should not be equal Autosave. The Support of case TS002312028 answered that this is working by design - Discard = Autosave + Move To Trash by design. Support confirmed that I correctly understood their answer. 

    I do not think that this is ER because DISCARD should not be equal to Autosave, however if IBM / HCL wants this to be ER, I don't mind.