What could be the scenario to use the new auditing function from Flow action Security tab? Cannot get the point from the official explanation.
Complete these optional fields to record each time a user requests this flow action. Each time the flow action is requested, your application can add an instance of the Log-DataAccessAuditclass, to support later compliance auditing, reporting, and analysis. The added instance identifies the date, time, Operator ID, flow action, Customer party (if any) and work item ID.
Logging occurs upon initial selection of the flow action, whether or not the flow action is completed. You can create report definition rules to report on Log-DataAccessAudit instances, or export the data for analysis.
(On the Display Options tab of the Harness form, you can provide a similar logging capability for user forms.)
Enable this feature only if detailed auditing is needed in your application. Auditing increases the database workload of your application and can produce large volumes of log data.
It would just record the invocation of flow action.
As it would record date, time, Operator ID, flow action, Customer party (if any) and work item ID it can be later used for troubleshooting behaviour of any particular business functionality if there are issue.
It can also be used in reporting for business usages.