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 Under Consideration
Workspace Domino
Created by Guest
Created on Feb 18, 2019

In the $UpdatedBy field, it is possible to continuously and accurately record the modification or save history of the document by the same user

The current standard features is that when the same user consecutively edited and saved the document, in the $UpdatedBy field of the document, it is impossible to accurately trace the user's continuous modification and save records. Because if it is a continuous modification or save by the same user, the system only records the user's modification or save of the document once in the $UpdatedBy field.
In order to more accurately record the user's modification or save history, I wishes to continuously record the user's modification or save history in the $UpdatedBy field.
  • Attach files
  • Guest
    May 5, 2021

    Probably because the names can be long, they are not saved in $UpdatedBy every time you edit, but only if they are different from the previous one. Times are as short as 8 bytes, so they are stored in $Revisions every time.

    It is required to store also the name so that the number of items in $UpdatedBy and $Revisions are the same.

    If you still want to save space, instead of a name that is the same as the previous one (and now not saved at all), only an empty item ("") could be saved. The volume of data would not increase much, but the history of change could be fully reconstructed.

    This could be optional in the database properties, similar to the number of items now adjustable:

  • Guest
    Feb 18, 2019

    Or support for track changes in audit purpose