This page contains the following buttons and fields:

Reject New Call checkbox	Specify whether or not to reject new calls during the work order.
Active Call Threshold field	This value is enabled only when Reject New Call is selected. Specify the threshold of active calls so that the software upgrade process can decide when to reboot the device.
Health Score Threshold field	Specifies the health score threshold, in percentage, with which to use to determine if the devices are in a stable condition. Note: This field is for HA pairs only.
Call shedding Timeout drop-down list	Specifies the time, in minutes, to allow for call shedding to reach the Active Call Threshold value. The minimum allowable value is 1 minute and the maximum is 60 minutes.
Restore Original Redundancy State After Upgrade checkbox	Select to restore original redundancy state after upgrade. Note: This field is only for HA pairs only.
Pause and Unlock after Loading Software (and Boot) Image(s) checkbox	This affects Push software image to the device within the Steps dialog. When this field is selected, the Push software image to the device within the Steps dialog is automatically selected. When this field is un-selected, the Push software image to the device within the Steps dialog is automatically un-selected.
Delete Old Software Image checkbox	When selected, the Oracle SDM Cloud removes the old software and/or boot loader image from the device upon a commit.
Steps icon	When clicked, this button opens a dialog box containing a list of process flow steps to be carried out by the work order task. Beside each step is a pause checkbox. Select the pause checkbox for any step at which you want the Oracle SDM Cloud to pause during the work order process.

1. Enter values for the Work Flow parameters.
2. Click Finish to complete creating the work order.

The following lists the steps the Oracle SDM Cloud takes during an NF upgrade work order:

Step 0: Check available space at the device	If there is available space at the device, the work order proceeds to the next step.
Step 1: Verify the original software image exists on device	Checks that the original software image (the current image) exists on the device.
Step 2: Push software image to the device	Uploads new software image to the device.
Step 3: Do call shedding on original active device	Starts the call shedding.
Step 4: Edit image name in boot parameters	Sets the new image name in the device boot parameters.
Step 5: Reboot the device	Reboots the device.

The following lists the steps the Oracle SDM Cloud takes during an SBC HA pair upgrade work order:

Step 0: Check available space for both devices	If there is available space on both devices, the work order proceeds to the next step.
Step 1: Check status and health for both devices	Checks that the health scores on both devices are within bounds.
Step 2: Verify the original software image exists on both devices	Checks the original software image (the current image) exists on both devices.
Step 3: Push software image to both devices	Uploads new software image to both devices.
Step 4: Do call shedding on original active device	Starts the call shedding on the active device.
Step 5: Edit image name in boot parameters for the standby device	Sets the new image name in the standby device boot parameters.
Step 6: Reboot the standby device	Reboots the standby device.
Step 7: Check health of the standby device	Checks the healthscore of the standby device.
Step 8: Force switchover active becomes standby	Changes both devices' redundancy roles. The standby device's redundancy role changes to 'Active'. The active device's redundancy role changes to 'Standby'.
Step 9: Do call shedding on original standby device	Starts the call shedding on the original standby device.
Step 10: Edit image name in boot parameters for the new standby device	Sets the new image name in the new standby device's boot parameters.
Step 11 Reboot the new standby device	Reboots the new standby device.
Step 12: Check health of the new standby device	Checks the healthscore of the new standby device.