If the change was made through BigFix, then it would be reflected in the action history, yes.
However, if a system is changed from a Compliant to a non-Compliant state, it is usually more likely that the change would have been made outside of Bigfix.
Take as an example some application that failed to install with UAC prompting turned on. It’s much more likely that a client administrator would turn off UAC in the local machine’s Control Panel, than thaflt they would call your administration and ask that it be disabled through BigFix. In that case BigFix will detect that UAC was disabled, and will report that through the Compliance module.
The Compliance interface would report the day on which it became non-compliant, Web Reports could have a report within a few minutes of when it became non-compliant (using the “last became relevant of fixlet ‘X’” report), but BigFix would not know who made the change.
You’d need to retrieve that through the Windows Auditing/event logs, usually through a SIEM such as QRadar, Splunk, etc.