Action Reasons

This page is accessed via Configuration and Administration > User Configuration > Manage User Access. In the User Access Type field select the option Action Reasons. Click on Edit User Access. The Action Reasons page opens.

You can configure Oracle Transportation Management so that when a specific user runs an action or agent action, they are prompted to specify a reason for doing so. The Action Reasons options on this page allows you to set this up.

See User Access Type for security hierarchy.

You can narrow down the action check to a specific:

• User ID
• User Role ID

Editing User Access

You can perform a reason check on specific actions per user role. This allows you to associate any number of actions with the user role. Each time the user tries to run this action, it prompts them to Record Reasons for running it.

1. Select the Prevent Access Changes check box to specify the final level for access configuration.
2. Specify the Audit Action ID for the action for which you want to set up the validation check.

   Note: Agent actions will have "(AGENT)" at the end of their description.

3. In the Requires field, select the level of detail required to enter for running the action. The options are:
   • Prompt: It will prompt the user, but no information is actually required.
   • Party: A Responsible Party is required.
   • Status: Responsible Party and Status are required.
   • Reason: Responsible Party, Status, and Reason are required.
4. Use the Reason Condition field to specify the condition that must pass in order for the action to be allowed.
5. In the Reason Plugin field, specify if you want the PARTY Java plugin to verify a condition, or none.
6. Click Save for each record you create.

Viewing Action Reasons

Action reason information is stored in the audit trail. You must have audit trail configured for your specific action in order to store/view this information. The event reason will then get stored on the corresponding Audit Record created by running the action.

Following is an example for the Change Service Provider action.

1. Configure Audit Trail functionality for the desired contact notification.
2. Create a contact with the communication method of AUD.
3. Edit the contact notification of SHIPMENT - ALTERNATE SERVPROV and assign the above contact with communication method of AUD.
4. Run the Change Service Provider action.
5. To view the audit, click the SmartLink from the shipment to Full Audit.