Announcement

Collapse
No announcement yet.

Merge 'update' entity notes

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Merge 'update' entity notes

    If someone makes a few changes to an Entity, Espo should check when creating a new note whether one of the same types exists in a configurable timeperiod (say 30 minutes), if one exists then update the existing note, setting a new timestamp, rather than create a new note.

    At the moment there is a note for every change.

    People quite often make many changes in quick succession, or click quick edit Update after adding every item, for instance.

  • #2
    I disagree. Very often you need to see exactly the little important change that was made amongst lots of others at almost the same time.

    But: An audit trail is by definition not a note, it should be searchable and only displayed on demand. I usually recommend to switch the audit trail on for ALL fields (you never know what you may need). Which creates tons of information and a needle in a haystack without a metal detector...
    ------------------
    Robert Laussegger
    iscon group
    http://www.iscongroup.net
    mailto://info@iscongroup.net

    Comment


    • #3
      What I'm suggesting would not lose any infomation.

      Two notes like this:

      Changed Title to Hello"
      Changed Cost to £1000

      And

      Changed Cost to £100000

      would be converted to

      Changed Title to Hello
      Changed Cost to £1000


      I agree about an audit trail being something a little bit different though.

      Comment

      Working...
      X