| HTML |
|---|
<div id="google_translate_element"></div>
<script type="text/javascript">
function googleTranslateElementInit() {
new google.translate.TranslateElement({pageLanguage: 'en'}, 'google_translate_element');
}
</script>
<script type="text/javascript" src="//translate.google.com/translate_a/element.js?cb=googleTranslateElementInit"></script> |
Holding Tank Management
How it Works
The "Process Holding Tank now" link will move any block assigned to "Holding" to its relevant "Available" pool. This command will process ALL addresses assigned to "Holding" depending on their age. The default time for release to "Available" is 30 days. If a block has not been in the holding tank for that specified length of time, it will not be released using this feature (it can be released manually per record at any time) . The threshold for the number of days in the Holding Tank is set in the main Admin Preferences page and is customizable.
...
| Info | ||
|---|---|---|
| ||
If you need to do a bulk "empty" of the holding tank. Set the time for release to "0" days. This will allow you to process the holding tank for all blocks that are in the Holding Tank. |
Holding Tank Permissions
For blocks with subassignments, the Holding Tank can utilize ProVision's permissions structure in order to override holding. This allows the subbassigned block to be set as assigned to the parent resource.
...
4) You will then see the 'Assigned To' field change from "Holding" to "Resource A", as the assignment is reverted to match the parent level.
| Note |
|---|
Override Holding through the permissions structure is intended only for blocks that are subassigned. It is not intended for blocks that are not subassigned. Setting holding permissions for non-subassigned blocks simply allows viewing of the block(s) in holding, and permissions do -not- extend to allowing overrides by design. |