Why does my trigger show a Last Updated timestamp that doesn't correspond to when I last edited the trigger? Follow

Comments

5 comments

  • Avatar
    DJ Jimenez

    When will this bug get fixed? Changing the trigger position doesn't qualify as an update as doesn't show up in the audit log. 

  • Avatar
    Jessie Schutz

    Hey DJ!

    I don't think that this is considered a bug, although I can definitely understand why it's not ideal. I'm going to do some hunting to see if I can find out whether this is something that could be changed, and whether we'd consider it. Sit tight!

  • Avatar
    Jessie Schutz

    Hi DJ! 

    I touched base with the Product Team, and here's what I was able to find out:

    They won't consider changing functionality so that re-arranging Triggers no longer counts and an update. Rearranging Triggers will impact their functionality and we have to maintain the integrity of the Trigger history.

    I asked about it not showing up in the audit log, and they said they would potentially consider changing that. First, though, they'll need to to do some research to find out whether it was left off the audit log for a specific reason, or if it was an accidental omission. They're adding it to their project backlog and will take a look at it when they can.

    I hope that helps! Let us know if you have any other questions.

  • Avatar
    DJ Jimenez

    Thanks Jessie,

    It'd actually be preferable to leave that event off the audit log. Although it would be useful to see that information, it would flood it. We have about 1300 triggers so if we moved a trigger from the bottom to the top it would post ~1300 updates to the audit log.

  • Avatar
    Jessie Schutz

    Hey DJ! It's entirely possible that this is why we left it out of the log in the first place. When the Product Team gets to a point where they're ready to start doing research on this I'll be sure to throw that out there!

Please sign in to leave a comment.

Powered by Zendesk