(imported topic written by dcheah)
When action parameters are used in actionscripts, there is no way to see what values were actually entered by the operators in their actions. Is there any way to have action history capture the actual values entered by the operators?
(imported comment written by SystemAdmin)
Hi dcheah!
Yes, it is possible to get the action parameter values that were entered but it is a little difficult. You’ll need to find the ‘Action X.fxf’ file in the Fixlet site and look inside the file. If you took your action as a master operator, you could find the file here:
Program Files\BigFix Enterprise\BES Client__BESData\actionsite
The ‘Action X.fxf’ file will use the action ID in place of the ‘X’ of course.
Inside this file, you’ll see lines that have your action parameter values.
Example:
action-parameter: “ClientSetting”="%3cExample Parameter Value%3e"
action-parameter: “action issue date”=“Tue, 10 Apr 2007 17:00:10 +0000”
(imported comment written by dcheah)
Thanks Tyler.
Is there any way that information can be retrieved from the BES Console? We would like to use the Action History as a sort of audit trail to what each operator did.
Or is that not what it is meant for?
(imported comment written by SystemAdmin)
Sorry dcheah, It isn’t available through the BES Console directly. The Action History can be used as an audit trail but the action parameter query can’t be figured out correctly on the BES Console in all cases. Sometimes the parameter will be dynamic and different for each computers, we could collect the parameter from each computer but the additional overhead of doing this probably isn’t worth the benefit.
A copy of the actions is maintained in the database so you could also find the action parameters in the database to preserve the audit trail.
(imported comment written by dcheah)
Thanks for your response.
We don’t really need to see what the relevance in the action evaluates to on each client but it would be useful if we can see what input each operator entered in the Action history in the Console itself.
As an example, we told our operators to take actions to stop a particular service using the Task, but if u look at the action history below, it’s not really possible to tell what service the operator actually stopped.
If possible, all we really need is to be able to tell what input the operator entered.
Action Script
Script Type application/x-Fixlet-Windows-Shell
action parameter query “ServiceName” with description “Please enter the service you would like to stop:” With default “”
dos net stop “{parameter “ServiceName” of action}”
Thanks.
(imported comment written by SystemAdmin)
Yep, this seems like it would be very helpful information to have. We’ll take a look at adding it to newer versions but for now the best you can do is find the .fxf file and get the value out of there.