1. Expand the Fraud Protection Manager slider and click Fraud protection list.
2. Click the Device association tab, select the Fraud Protection List (FPL) that you want to modify and click Edit.

   Note:

   If the push task cannot be edited because it is configured or you not have permission to modify it, this Edit button changes to View and the Edit FPL push task configuration pane is in read-only mode.
3. In the Edit FPL push task configuration pane, you can modify the following fields:

   Name field	(Read-only) The unique, user-specified name assigned to the push task that is an alpha-numeric value from 1 to 24 characters in length with no spaces.
   Task typedrop-down list field	Select from the following push task types: On demand— Start the task anytime. Schedule— Plan a specific time to start the task. Auto FDP—No user intervention required. FPL updates are pushed regularly to Oracle Communications Session Delivery Manager (SDM) from the Fraud Detection and Prevention (FDP) device. SDM reconciles these updates with the specified FPL and pushes the result after reconciliation to the device(s). If the reconciliation fails, then an error is logged. If the pass through status of the FPL push task is NotScheduled or Committed then the pass through push task is allowed to start immediately (the Start now status).
   FPL drop-down list	Select the Fraud Protection List (FPL) name that is applied to the device(s).
   Start date and time field	This option is available only if the Task type is Schedule. Select a start date for the push task is scheduled to start by clicking the calendar icon and specify time entries in the Time fields by selecting the hour, minute and second respectively by typing the numbers in the text box or using the arrows.
   Auto commit checkbox	You can use this option if the Task type is On demand or Schedule only. If the Task type is set to Auto FDP, the auto commit function is on automatically and cannot be modified. When a push task completes, but is not committed, it retains a lock on all its targeted devices so that no other operations can be performed on them until the push task is successfully committed and its devices are unlocked. Check the check box to automatically commit the push task after the successful execution of the push task. If the check box is unchecked, you have to manually commit the push task. Refer to the Commit a Fraud Protection List Push Task Manually section for more information.

4. In the Device group tasks table and select the Network Function (NF) and click Manage to edit device in the push task.
5. In the Select Device dialog box, expand a device folder in the Managed devices table, select a device row, and click Add to add an additional device or if you want to remove a device from the push task, select the device row and click Remove.

   The device, its network function and folder structure moves to the Targeted devices table and the folder structure is collapsed.

   • The device must be capable of using the fraud protection feature.
   • A push task is limited to one platform and software version at a time.
   • In the case of an HA device pair, the FPL push task is applied to both devices.

   Note:

   If you receive a Warning message that says the FPL file on the device you adding does not match the FPL that you are using for the push task, you must use Configuration Manager or the device ACLI to change the FPL file name on the device to match the FPL of your FPL push task in order for the FPL push task to be used with the device you are adding. Refer to the device documentation for more information about changing the FPL file name on the device.
6. Repeat the previous steps to add or remove additional targeted devices. Up to twenty devices can be added to a push task.

   Note:

   Device filtering is applied after the first device is selected.
7. Click OK. The device(s) appear in the Device group tasks table, which displays the network function (NF) name and its device(s).
8. Click Apply.
9. In the success dialog box, click OK.
   The changes that you made appear in the FPL push tasks table.

A Fraud Protection List (FPL) push task can be committed manually if the Auto commit checkbox is not checked in the FPL push task configuration pane.

1. Expand the Fraud Protection Manager slider and click Fraud protection list.
2. Click the Device association tab and select an FPL push task from the FPL push tasks table and click Commit.
3. In the confirmation dialog box, click Yes.
4. Click Refresh to confirm the FPL push task status changed from Success to Committed.

When the Fraud Protection Manager is configured to automatically push notifications to devices, any user changes made to a Fraud Prevention List (FPL) are delivered to the devices on the next incident reported by the FDP that is registered to the FPL.

Until the FPL push task is committed, you can stop it and perform a rollback to restore the original configuration settings if the push task is in a WaitStarting, Failed, Success or Scheduled state.

1. Expand the Fraud Protection Manager slider and click Fraud protection list.
2. Click the Device association tab, and select the FPL push task that you want to roll back from the FPL push tasks table and click Abort.
3. In the confirmation dialog box, click Yes.

When a Fraud Protection List (FPL) push task is executed successfully, it cannot be modified, which includes adding devices. However, you can copy an existing FPL push task and save it as a new FPL push task. The new FPL push task can then be applied to a different set of devices. Copies of an FPL push task can be used to divide large numbers of devices into smaller groups of devices that repeat the same push task.

1. Expand the Fraud Protection Manager slider and click Fraud protection list.
2. Click the Device association tab, and select the FPL push task that you want to copy from the FPL push tasks table and click Copy.
3. In the Copy FPL push task configuration pane, provide a new name for the push task and make any other changes for the new FPL push task. See the Edit a Fraud Protection List Push Task section for more information about modifying these parameters or adding or removing devices.
4. Click Apply.
5. In the success dialog box, click OK.
   The changes that you made appear in the FPL push tasks table.

You can resubmit a push task to start execution for the targeted device group network function (NF) if the status of the push task is in the Failed, ResetToReady, or RollbackFailed state.

1. Expand the Fraud Protection Manager slider and click Fraud protection list.
2. Click the Device association tab to access the Fraud Protection List (FPL) push task information.
3. In the Device group tasks table, select the push task row and click Resubmit.

1. Expand the Fraud Protection Manager slider and click Fraud protection list.
2. Click the Device association tab to access the Fraud Protection List (FPL) push task information.
3. In the FPL push tasks table, the following column information displays all the push tasks configured in SDM:

   Name	The alpha-numeric, unique, user-specified name assigned to the push task.
   Device count	The number of targeted device nodes (standalone devices or HA pairs) the push task executes. An HA pair is considered one device node.
   FPL	The Fraud Protection List (FPL) name that is applied to the device(s).
   Status	A push task can have the following status: PartiallyConfigured—The configuration is incomplete. This can also be the initial state of a copied push task. NotScheduled—The push task start time is not yet configured by the user. Scheduled—The push task start time is configured and scheduled to begin at a specified date and time. WaitStarting—The scheduled push task is placed into a run-waiting queue by the server's scheduler and awaits the scheduled time to start running. Running—The push task started and is currently processing. Success—The push task execution completed successfully, but has not yet been committed. Failed—The push task failed during execution. StartCommitting—The push task started the process of committing the designated changes after the Committed button was pushed. Committing—The push task is in the process of committing the designated changes. Committed—The changes were executed successfully by this push task and are now committed. CommitFailed—The push task failed to commit and some of the locked resources or the auto-generated files may fail to remove. StartAborting—The push task is in the beginning process of aborting after the Abort button is pushed. Aborting—The push task is executing the abort process. Aborted—The push task has been successfully aborted. All changes made on all targeted devices are rolled back and the devices retain their original state prior to the work order execution. AbortFailed—The push task failed to abort due to a failure of a device rollback process. LockingResource—The state when the push task locks all necessary resources. LockResourceFailed—The push task failed to lock all necessary resources. You can restart the work order in this state.
   Start time	The server start date and local time for the push task.
   End time	The end time is the server local time when the following conditions occur for this push task: The work order finished successfully and paused. A failed condition has been met and the work order stopped as a result of the failure. The user manually stops a work order already in progress.

The Device group tasks table displays a summary of a the best-effort device tasks that are launched or scheduled to be launched in parallel for the selected push task in the Fraud Protection List (FPL) push tasks table.

1. Expand the Fraud Protection Manager slider and click Fraud protection list.
2. Click the Device association tab to access the Fraud Protection List (FPL) push task information.
3. In the Device group tasks table, view the following column information:

   Name	Description
   Network function	The name of the network function (NF) to which the device(s) belong.
   Device group	The device group name.
   Status	A device task can have the following status: Ready—The push task is ready to run and waiting for the SDM scheduler to initiate the push task to start on the device. ResetToReady— When the push task restarts, all the failed tasks are reset to this state to distinguish the initial Ready state of the device task. Starting—The intermediate state between the Ready and Running states when users submit or resubmit the device task. Running—The push task started and is currently processing. Success—The push task completed successfully. Failed—The push task failed during execution and any changes are rolled back. RolledBack— The push task is rolled back successfully. RollBackFailed—The push task is rolled back unsuccessfully.
   Start time	The SDM server start date and local time at which the push task was scheduled to start or the time when a task within a push task is started. The following criteria are used: If the push task has not reached its scheduled start time to start all individual tasks for this push task to display the same start time. When an individual push task starts, it replaces the scheduled start time with the time it started processing.
   End time	The end time is the server local time when the following conditions occur for this device task: The device task finished successfully and paused. A failed condition has been met and the device task stopped as a result of the failure.

   Note:

   If any one of the devices fail to do FPL file updates, then the device is automatically rolled back to the original FPL file.
4. (Optional) Click Refresh to update the contents in the Device group tasks table.
5. (Optional) Select an NF from the Device group tasks table and click Logs to view logs for the targeted device group node. Logs are maintained separately for each device group in the table.

1. Expand the Fraud Protection Manager slider and click Fraud protection list.
2. Click the Device association tab, click Search.
3. In the FPL push task search dialog box, complete any of the following fields:

   Name field	The unique, user-specified name assigned to the push task that is an alpha-numeric value from 1 to 24 characters in length with no spaces.
   FPL field	The Fraud Protection List (FPL) name that is applied to the device(s).
   Status field	You can filter on any of the following push task status entries: PartiallyConfigured—The configuration is incomplete. This can also be the initial state of a copied push task. NotScheduled—The push task start time is not yet configured by the user. Scheduled—The push task start time is configured and scheduled to begin at a specified date and time. WaitStarting—The scheduled push task is placed into a run-waiting queue by the server's scheduler and awaits the scheduled time to start running. Running—The push task started and is currently processing. Success—The push task execution completed successfully, but has not yet been committed. Failed—The push task failed during execution. StartCommitting—The push task started the process of committing the designated changes after the Committed button was pushed. Committing—The push task is in the process of committing the designated changes. Committed—The changes were executed successfully by this push task and are now committed. CommitFailed—The push task failed to commit and some of the locked resources or the auto-generated files may fail to remove. StartAborting—The push task is in the beginning process of aborting after the Abort button is pushed. Aborting—The push task is executing the abort process. Aborted—The push task has been successfully aborted. All changes made on all targeted devices are rolled back and the devices retain their original state prior to the work order execution. AbortFailed—The push task failed to abort due to a failure of a device rollback process. LockingResource—The state when the push task locks all necessary resources. LockResourceFailed—The push task failed to lock all necessary resources. You can restart the work order in this state.
   Start time field	The server start date and local time for the push task.
   End time field	The end time is the server local time when the following conditions occur for this push task: The work order finished successfully and paused. A failed condition has been met and the work order stopped as a result of the failure. The user manually stops a work order already in progress.

4. Click OK.

A Fraud Protection List (FPL) push task can be manually deleted only if it is in the PartialConfigured, NotScheduled, Aborted, or Committted state.

1. Expand the Fraud Protection Manager slider and click Fraud protection list.
2. Click the Device association tab, and select the FPL push task from the FPL push tasks table and click Delete.
3. In the confirmation dialog box, click Yes.