Currently when resolving conflicts when saving changes to projects, you have no idea who made the changes in conflict or on what timestamp.
Can the username and date/time stamp please be added into here?
3 Likes
Along those lines, would be nice to be able to configure a 'designer timeout' of some kind. E.g. if a user has a view open and doesn't actually do anything in it, auto close it after a period of time so they don't accidentally have it open in the background when they hit save and create conflicts.
The timestamp would be easy enough to add (the OS can give us that), but the user is a bit more problematic. We don't currently track the logged-in user who makes a change, and files can be changed by anyone with file system access without being logged in to Ignition. Even if we added user info to a resource, I'm struggling to think up a way to keep a good accounting of the user that could handle both of these sources of truth and be useful to you.
1 Like
I guess I'm thinking more editing from the designer, as raw file manip is far less frequent. If we do that then I think it's also fair to expect us to handle updating the resource file as well
2 Likes
Just omit the user if the change was noticed in the filesystem. Include it when known. Any tooling that looks for it would have to handle it being missing for backwards compatibility, so should be reasonable going forward. Any external tooling that knows the user on that side, and regenerates the resource meta data (grrrr) could supply it, too.
2 Likes
Personally I still think there should be a save and a save all. And some way to locate opened and closed but not saved yet resources, as I lose them sometimes especially if they're nested in folders. Only way currently is to go hunting for italics
2 Likes
This is exactly what I do in my resource generation library.
And if the last modification actor isn’t meaningful enough to be shown in the designer, then why does it exist at all?
1 Like
???
As for the main topic of the thread - we do indeed already track a 'LastModification' (best effort) based on the Designer user or detected filesystem operation; we could definitely display that to the end user in this conflict resolution dialog (and elsewhere in the designer, as both you and Amy have engaged with: Add Last Modified info to Views/Windows/Templates | Voters | Inductive Automation 
)
5 Likes
Neat -- glad to see we've added that since I last worked on that system.
1 Like
Is it possible to see the last edit on the project list in the gateway?
Config> System> Projects