Audit Actions

This page is accessed via Business Process Automation > Power Data > Event Management > Audit Actions.

Use the Audit Actions page to set up validation checks for an action before it is actually processed. For example, you may want to run a particular shipment action only if the shipment is of a certain status.

You cannot add new audit actions.

Note: You can also set up validation checks based on user role in the User Access Manager.

1. Select an Audit Action Type.
2. Use the Allow Condition field to specify the condition that must pass in order for the action to be allowed.
3. Specify in the Allow Plugin field if you want a use a self-created Java plugin to verify a condition.
4. The Cause and Solution fields specify what is displayed when the validation check fails.
   For example, without these fields populated, the error may display as:
   
   You cannot perform this action. The following records failed the DOMAIN.TEST check: [ DOMAIN.XXX]
   
   With these fields populated, the error may display as:
   
   You are trying to add a new port location. You are not allowed to add a new port location.
5. The Post Action Check check box is not used.
6. The Support Post Check check box should not be edited.
7. If you do not want the audit action to lock the database, make sure that the Allow Lock check box is cleared.
8. If the Allow Lock check box is selected and you want to override the default Lock Timeout, enter a new time. If your audit action is locked for that long, then it automatically unlocks after that time. If the lock timeout value is blank and the Allow Lock check box is selected, then the system reads the timeout value from the glog.objectLock.waiterTimeout.duration.activity property. The Allow Lock check box on the Data Query Type page overrides the audit action Allow Lock check box.
9. The Lock Polling field and the Application Name field are not used.
10. The Data Query Type ID field should not be edited.
11. The Power Action and Power Action Name are for actions on the Dock manager.

Responsible Parties

1. Use this section to assign Responsible Party Profiles to the Audit Action. A responsible party profile is a set of responsible parties that have something in common and are responsible for an action or issue.
2. If you use the "All" responsible party profile that is part of public data, and you want to exclude a small set of others, then select another responsible party profile in addition to "All" and check Exclude for it. This will include everyone that is part of "All" with the exception of those defined in the second responsible party profile.

Note: When you select an audit action of ADD TRACKING EVENT, any responsible party profiles you enter and select Exclude will be unavailable from the tracking. By setting a responsible party to Exclude, you are effectively limiting the list of available responsible parties on the tracking screen, thereby limiting status code and all downstream associated options.

Note: To add responsible parties for Add Event actions for the driver, equipment, power unit, and shipment tracking event, you must add the responsible party profiles to the ADD TRACKING EVENT audit action.