Able to Click OK and not Save when Adding an Order Release to a Job, it Looks like the Order Release has been Saved but it has not. (Doc ID 1298680.1)

Last updated on SEPTEMBER 08, 2016

Applies to:

Oracle Forwarding and Brokerage Operations - Version: 6.1.3 and later   [Release: 6.1 and later ]
Information in this document applies to any platform.

Symptoms

On OTM version 6.1.3 when adding an Order Release to a Job, if SAVE is not clicked the UI still leads the user to think the Order Release has been saved to the job when they click on the 'OK' button.

EXPECTED BEHAVIOR
-----------------------
Expect an error to be displayed letting the user know that the data in the Grid has not been saved.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1 - Log onto an OTM 6.1 system.

2 - Navigate to: Brokerage and forwarding > Job Management > Job Details.

3 - Click on the N to create a new Job.

4 - Enter the ID for the new Job and Type is set to 'Order Release'.

5 - Click Finished.

6 - Navigate to: Brokerage and forwarding > Job Management > Job Details and enter the Job ID created in step 4.

7 - Click the 'Go/refresh' button.

8 - Click on Actions > Add Orders to Job > enter the ID of an existign Order Release.

9 - DO NOT CLICK SAVE.

10 - Click on 'OK'.

Expectation is an error is to be displayed stating objects in the grid have not been saved.

11 - A message stating "Confirmation Selected orders have been added to the job." is displayed.

12 - Return to the Job UI and clicked the "Go/Refresh" button and the Order is not saved to the job.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms