| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| checkpoint:build [2018/12/17 01:16] – [Movement Tree] Scott Cunliffe | checkpoint:build [2025/01/21 22:07] (current) – external edit 127.0.0.1 |
|---|
| ====== Movement Tree ====== | ====== Movement Tree ====== |
| |
| The Movement Tree provides a list of all available movements, organized in the hierarchy of Server, [[object:customer|Customer]], [[object:media|Media Type]], Receiving [[object:repository|Repository]], and Sending [[object:repository|Repository]]. | The Movement Tree provides a list of all available [[object:volume|Volume]] movements, organized in the hierarchy of Server, [[object:customer|Customer]], [[object:media|Media Type]], Receiving [[object:repository|Repository]] and/or Sending [[object:repository|Repository]]. |
| |
| Any [[object:customer|Customers]] with a [[object:repository|Repository]] with the ''Do not slot'' option set to true will display with a purple background. | Any [[object:customer|Customers]] with [[object:volume|Volumes]] moving to a [[object:repository|Repository]] with the ''[[master:repository_options|Do not slot]]'' option set to ''True'' will display with a purple background (eg. US03). |
| |
| {{checkpoint_customer_tree.png}} | {{checkpoint.png}} |
| |
| ===== Build/Update Movement Tree ===== | ===== Build/Update Movement Tree ===== |
| |
| When you first [[desktop:logon_window|login]] to Checkpoint all current movement data will be automatically loaded into the movement tree. As new movements can be added to TapeTrack at any time it is advisable to refresh or reload the data in the movement tree to ensure displayed volumes are up to date. | When you first [[desktop:logon_window|login]] to Checkpoint all current movement data will be automatically loaded into the Movement Tree. As new movements can be added to TapeTrack at any time it is advisable to refresh or reload the data in the Movement Tree periodically to ensure displayed [[object:volume|Volumes]] are up to date. |
| |
| <note important>Updating the Movement Tree will clear any volumes in the **To Scan** window</note> | <note important>Updating the Movement Tree will clear any [[object:volume|Volumes]] in the **To Scan** window</note> |
| |
| To refresh the movement tree select, from the main menu, ''Process'' -> ''Build/Update Movement Tree''. | To refresh the Movement Tree select, from the Main Menu, ''Process'' -> ''Build/Update Movement Tree''. |
| |
| {{checkpoint_process_update_tree.png}} | {{refresh_tree_main.gif}} |
| |
| Refreshing the movement tree can also be done by: | Refreshing the Movement Tree can also be achieved by: |
| * Right clicking a customer and selecting ''Rebuild''.{{checkpoint_right_click_update_tree.png}} | |
| * Pressing F5 while movement tree in focus. | |
| |
| After you exceed the time threshold Checkpoint will automatically prompt you to refresh the movement tree when adding volumes to the **To Scan** window. | Right clicking any [[object:customer|Customer]] and selecting ''Rebuild''. |
| | |
| | {{rebuild_tree.gif}} |
| | |
| | Pressing F5 while Movement Tree in focus. |
| | |
| | After you exceed the time threshold Checkpoint will automatically prompt you to refresh the Movement Tree when adding [[object:volume|Volumes]] to the **To Scan** window. |
| |
| {{checkpoint_rebuild_tree_warning.png}} | {{checkpoint_rebuild_tree_warning.png}} |
| |
| <note important>Updating the Movement Tree will clear any volumes in the **To Scan** window</note> | <note important>Updating the Movement Tree will clear any [[object:volume|Volumes]] in the **To Scan** window</note> |
| |
| <- checkpoint:login|Logging In ^ checkpoint:starting|Getting Started ^ checkpoint:pick|Pick (Send) -> | <- checkpoint:login|Logging In ^ checkpoint:starting|Getting Started ^ checkpoint:pick|Pick (Send) -> |
| |
