Logging Operator Actions?

[getrich]

Hi all,

I was wondering if there was a simple way to log all user actions, including those on the GUI (the default full-featured or simple GUI examples are fine). I checked the 2017 Help Documentation, but did not find anything specific to logging user actions on the software. I understand that this could possibly be more of a C# question as it deals with the GUI, but I thought I'd try to see if anyone off the top of their head knows an easy way or if TestStand has this capability already. Thanks!

[~jiggawax~]

Are you wanting to track every button they click on the UI?  Or do you want to track only what happens in the execution of the sequence file?

There are a couple options for UI tracking:

Option 1 - Add an event for each button and log to a file every time they click on it.

Option 2- Use UIMessages and track everything that comes accross there.  More on UIMessages here: http://www.ni.com/tutorial/4532/en/ 

Maybe if I understand what you would be using the data for I could give you a better solution.

[James_Grey]

It doesn't cover everything, but a central place you could take note of a lot of user actions is in an event handler for ApplicationMgr.PostCommandExecute ( command)

[getrich]

jigg, thanks for your input. I am actually already using UIMessages to post specific results to the external GUI, so that would be a good option to explore.

Basically I think we just want to log every button that the user interacts with on the UI, including if they modify run options in the SequenceView (e.g. if they set a specific step to "Normal", "Skip", "Force Pass", "Force Fail", and which step it was that they modified). Appreciate your input so far!

[getrich]

James, thanks for making me aware of the PostCommandExecute event. It does seem to log actions made in the SequenceView, which is a plus for what we are trying to do. Appreciate your help!

[~jiggawax~]

Why wouldn't you use credentials so they can't change those things?

[ee-jallen]

Correct, Why not use the User Manager and Privilege settings to control who can modify files.  Also other third party file checksum utilities can be employed to verify that that test files were not modified before the test started.