Log Event upon Impactful Workflow Action
While changes in asset Statuses and asset Commands are automatically logged, to give the logs a clearer picture, it is recommended to log any impactful events that occur during a Workflow.
- Control Transfer of a Workstation - if an operator needs to leave their desk, another operator can take control of that Workstation until the previous operator returns. This should be reported as it pertains to the security of the facility.
- Max Log In Attempts Exceeded - when there have been too many login attempts, the application can lock the user out and prevent them from accessing the system. This should be recorded in case of repeat attempts.
- Notify Maintenance of False Alarm - documenting false alarms helps identify and correct causes, preventing future disruptions.
If it is an action that will directly impact people or a situation that needs context, it should be logged, since the log entry can serve as a reference point to determine the actions taken by the Workflow. This approach gives detail and context to the situation and makes it easier to understand the audit trail when reviewing the logs. To create a custom log message, Action blocks are needed. Here is the recommended general implementation:
This will record a log entry of the announcement. To implement this Workflow, go to the Write Custom Logging Message page.