Status Change trigger of a workflow

In classic workflow, we have Record Status change among many other events those can be used to trigger the workflow. 

Though we have two fields for status change namely Status and Status Reason, trigger works only for Status, but not for Status Reason. In most cases this is actually record Deactivation or Activation. If you need to trigger a workflow for Status Reason we need to use Record Field Change event as we do for any other field.

Why talk classic Workflows, but not cloud flows/ power automate?

Previously we thought classic workflows will be history by now with introductions of Cloud Flows. Though cloud flows are pretty powerful in terms of collection of connectors we can use etc. Anyway, still its not helping the developers in many way;

• Connection strings are still a complete mess that easily jeopardies a deployment
• When logic of Cloud Flow is growing, the illustration becomes very big and not easy to have a one view even via a big monitor. 

As per this writing, classic workflows still running in most of the implementations of the world and no sign of getting replaced that easily for a long time.

A big loophole in field level security !

We all use field level security as a trustworthy way of hiding selected fields from an entity where user could have the access rights for remaining fields. 

Typical scenario could be, Contact entity is a very generic type yet you could have sensitive details such as salary, bank details or marital status etc. Here field level security come in handy since you can hide only those fields for selected users.

Loophole

Well..keep in mind if users are allowed to check audit history of the record, irrespective of field level security setting, user will see all the audit details of all the fields those are enabled for auditing. This is not ideal isn't it?  :-(