7 Using the On Hold Worklist

The On Hold Worklist enables workflow managers and intake processors to review records that have been put on hold.

Overview

Whenever the Oracle Safety One Intake system is unable to add a follow-up record to a case, the record is put on hold and is accessible through the On Hold Worklist.

Follow-up records can be put on hold for the following reasons:

Table 7-1 Reasons for records to be put on hold

Reason	Description
Case in workflow state not accepting follow-up merge	The current workflow state of the case is configured to not accept Follow-up Merge. For more information, see Configuring Case Workflow in Oracle Argus Safety Administrator's Guide.
Case is locked	The case is locked and cannot currently accept follow-up documents. For more information on lock or unlocking cases, see Lock or unlock a case in Oracle Argus Safety User's Guide.
Case is in use	The case is currently open and a different user is working on it. The system may also still be working on the case.

Records can be put on hold manually or automatically:

• Whenever a user accepts a follow-up record, but the destination case cannot accept a follow-up record due to the reasons outlined above, Oracle Safety One Intake prompts the user to either put the record on hold or discard it altogether.

• If Auto-Accept is enabled and the destination case cannot accept a follow-up record due to the reasons outlined above, the record is automatically put on hold.

  Note:

  Your administrator is responsible for configuring the Auto-Accept feature on a source by source basis.

Once the reason is lifted, the record is returned to the normal Oracle Safety One Intake flow.

• Work with records that are on hold
  As an intake processor or a workflow manager, using the On Hold Worklist, you can find out in more detail why a record has been put on hold.