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

Add a new idea Subscribe
Status Under Consideration
Workspace Notes
Created by Guest
Created on Dec 17, 2018

RELATED IDEAS

Provide option for field level change tracking

$UpdatedBy and $Revisions can tell us when and who acted on a document, but there is certainly a use case that comes in the subsequent question "But can you tell us what that person changed on that date?" 

Something like that can be coded, but it rarely is an upfront requirement. The situation usually comes up after the fact and occasionally accompanied a knife twist of "well other platforms show me what was changed in a session". Usually happens around high stakes or HR/confidential situations where having immediate insight to prior record changes would improve everyone's day.

  • Attach files
  • Guest
    Reply
    |     Sep 9, 2020

    A possible useful variation of this would be the option to highlight changes in field data, though this could be left to the programmer if the change data was made available.

  • Guest
    Reply
    |     Sep 9, 2020

    This! It would be good to have this set on a field level as the size of the tracking information could grow quickly and many fields may not be of interest if they change.

    This is something that developers have to write over and over again due to the lack of the ability to log changes through a built-in mechanism.

  • Guest
    Reply
    |     Dec 18, 2018

    This would be a useful feature to have, especially for instances where revision history is a known requirement.  I can see this as potentially being resource intensive as the initial document state would need to be saved so changes can be identified.  I would like to see it as a database option that can be enabled if required.  Possibly store the history in a companion NSF file to help keep the application document count down.

Copyright © 2023 HCL Technologies Limited