You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to suggest that we add 1 or more fields to the FGMJ project file, to identify the version of WISE Builder and EXE that produced and handled the file.
If Builder built the file, then it should insert a version string so it's clear what built it.
If WISE.EXE later saved out the file, then it should insert a string so that's also clear. This field may want to be an array to track multiple saves of the file. Otherwise, we need to define if it's the first time the file is saved by WISE.exe, or the last time it's saved out.
A 3rd field may be useful if you want to track other tools that may modify the file. But the 2nd field may be suitable if it's not limited to just WISE.
A date/time with creation and each save may be useful too. User or system ID's may be interesting but may become protected data if you look at the user ID of the (Linux) account handling the file, so that may be too far.
How will this improve the project or tool?
Provide an audit trail on how a file was created, and maybe saved out, to track possible bugs that need fixed in files, revision control, etc. We already store a version field for the version of the file, but not of the components that touch it.
Approvals Process
Testing For Issue
Executive Approval
Merge
Provide Attribution
The text was updated successfully, but these errors were encountered:
Contact Details
[email protected]
What is needed?
I would like to suggest that we add 1 or more fields to the FGMJ project file, to identify the version of WISE Builder and EXE that produced and handled the file.
If Builder built the file, then it should insert a version string so it's clear what built it.
If WISE.EXE later saved out the file, then it should insert a string so that's also clear. This field may want to be an array to track multiple saves of the file. Otherwise, we need to define if it's the first time the file is saved by WISE.exe, or the last time it's saved out.
A 3rd field may be useful if you want to track other tools that may modify the file. But the 2nd field may be suitable if it's not limited to just WISE.
A date/time with creation and each save may be useful too. User or system ID's may be interesting but may become protected data if you look at the user ID of the (Linux) account handling the file, so that may be too far.
How will this improve the project or tool?
Provide an audit trail on how a file was created, and maybe saved out, to track possible bugs that need fixed in files, revision control, etc. We already store a version field for the version of the file, but not of the components that touch it.
Approvals Process
The text was updated successfully, but these errors were encountered: