We’ve had a few instances where a user drags a rule incorrectly to a different location in ETL. Maybe we could create an ‘undo’ button to revert the indexes?
Because the Index is stored in the Database, we would need to store the PREVIOUS ID and the CURRENT ID in order to know what to revert too.
The IDs are hidden because the actual number is irrelevant - the Relative order is what matters, so dropping a row in the wrong place would have no effect on the order of the other rules…. I just may take a moment to find the rule you just moved?
jay.hornback@syniti.com
•
Apr 27
At the very least could we get the ‘modified by/on’ values to log the change?
As far as the previous/current id: what about an ‘activity log’ of some type? It could log each action, at least per session: adding a rule, changing the order, deleting a rule, etc.
I could see value in this if you wanted to unwind a few changes… and in our case we have some targets with 50+ update rules. So the use case for the customer user that asked for this was - they accidentally dragged a rule down and only saw it out of the corner of their eye. It was likely not impactful but really hard to tell which one was moved.
Log in to comment and vote
Comments2
John Munkberg
Apr 25
Because the Index is stored in the Database, we would need to store the PREVIOUS ID and the CURRENT ID in order to know what to revert too.
The IDs are hidden because the actual number is irrelevant - the Relative order is what matters, so dropping a row in the wrong place would have no effect on the order of the other rules…. I just may take a moment to find the rule you just moved?
jay.hornback@syniti.com
Apr 27
At the very least could we get the ‘modified by/on’ values to log the change?
As far as the previous/current id: what about an ‘activity log’ of some type? It could log each action, at least per session: adding a rule, changing the order, deleting a rule, etc.
I could see value in this if you wanted to unwind a few changes… and in our case we have some targets with 50+ update rules. So the use case for the customer user that asked for this was - they accidentally dragged a rule down and only saw it out of the corner of their eye. It was likely not impactful but really hard to tell which one was moved.