You can remove a disposition hold placed on an entity to restart execution of its disposition schedule.
To determine the type of hold on an entity, browse to the entity, right-click, select Get Info, and click Holds. If the IsDynamic value is False, the hold is manual, and you can remove the hold manually or through the command line. If the value is True, the hold was placed by Hold Sweep and you can only remove the hold by executing Hold sweep.
You can remove a manual disposition hold from the information page of either the entity or the hold.
To remove a hold using the entity's information page
To remove a hold using the hold's information page
If you cannot remove a hold manually, then the hold was probably applied by Hold Sweep. Hold Sweep can take over a manually applied hold if the hold's conditions were met by the entity. In that case, use the following procedure to remove conditional holds.
You can remove conditional holds by initiating a hold request, and running Hold Sweep. Generally, you would let the scheduled Hold Sweep run when system usage is low.
Once you've requested that the holds be removed in the next Hold Sweep run, you can also cancel this request before the next Hold Sweep runs. Once Hold Sweep has removed a conditional hold on an entity, the entity receives a flag that tells Hold Sweep not to put it on hold again. If you do want to put it on hold again, you can reactivate it for hold processing. See To reactivate a hold request.
To initiate a Remove Hold Request
To cancel the remove hold request
After setting a remove hold request, you can cancel it before the next Hold Sweep run. This way the entities will remain or be placed on hold again.
After you select Cancel Remove Hold Request, then run Hold Sweep, the hold's context menu displays Activate for Hold Sweep Processing. Selecting this option sets the hold to be processed during the next Hold Sweep. This is also the way you could put an entity back on conditional hold during the next Hold Sweep run.
Instead of setting up the hold names and GUIDs in the configure mode, you can just specify everything in one command. When you remove holds this way, they apply regardless of whether the hold is active or inactive and regardless of whether they were applied manually or by Hold Sweep. You must specify the following in the command.
For example:
Windows
RecordsManagerSweep.bat -HoldSweep -ObjectStore "FPOS Name" -ForceRemoveHold "Hold1|Hold2|{E4F6F8F9-4E1A-4762-B062-344980B2B92}"
Unix
./RecordsManagerSweep.sh -HoldSweep -ObjectStore "FPOS_name" -ForceRemoveHold "Hold1|Hold2|{E4F6F8F9-4E1A-4762-B062-344980B2B92}"
CAUTION Alternatively, you can use the -All option with -ForceRemoveHold to remove all holds across the entire object store. This option removes all holds regardless of whether they are active or inactive or whether they are conditional or manual. This would only be used for a special purpose.
RecordsManagerSweep.bat -HoldSweep -ObjectStore "FPOS Name" -ForceRemoveHold -All
Removing a hold from empty containers can cause the hold's Conditions information page to become read only. This happens if you:
Either of these cause the hold to become inactive for Hold Sweep processing. You must activate the hold by selecting Activate for Hold Sweep Processing from the hold's context menu.