Description | Represents the following types of security classification objects that support Department of Defense (DoD) classified records:
NOTE These objects are only used with the DoD Classified Records Data Model (Chapter 4). |
Deployment Mechanism | Use the File Plan Import Export tool to deploy classification guides, sections, and topics from the File Plan object store (FPOS) in the source environment to the FPOS in the destination environment. You can use the File Plan Import Export tool to deploy only the file plan, only the supporting objects in the file plan, or both the file plan and supporting objects. For more information about this tool, see Expansion Products > Records Manager > File Plans > How to > Use the File Plan Import and Export Tool. |
Dependencies | None |
Notes | The File Plan Import Export tool does not reuse GUIDs when it creates objects in the destination FPOS. However, the tool correctly matches the objects and, depending on the mode in which you are running, takes one of the following actions:
|
Description | Represents the following types of container objects:
|
Deployment Mechanism | Use the File Plan Import Export tool to move file plan containers from the FPOS in the source environment to the FPOS in the destination environment. You can use the File Plan Import Export tool to deploy only the file plan, only the supporting objects in the file plan, or both the file plan and supporting objects. For more information about this tool, see Expansion Products > Records Manager > File Plans > How to > Use the File Plan Import and Export Tool. |
Dependencies | To completely re-create containers in the destination environment, you must also import the related schedule information. You can import the schedule information separately or in tandem with the import of the containers. For more information, see Record schedule information. |
Notes | The File Plan Import Export tool does not reuse GUIDs when it creates objects in the destination FPOS. However, the tool correctly matches the objects and, depending on the mode in which you are running, takes one of the following actions:
|
Description | Represents the following types of objects related to schedules. These objects are stored as custom objects in the Content Engine.
|
Deployment Mechanism | Use the File Plan Import Export tool to move schedule objects from the FPOS in the source environment to the FPOS in the destination environment. You can use the File Plan Import Export tool to deploy only the file plan, only the supporting objects in the file plan, or both the file plan and supporting objects. For more information about this tool, see Expansion Products > Records Manager > File Plans > How to > Use the File Plan Import and Export Tool. |
Dependencies | None |
Notes | The File Plan Import Export tool does not reuse GUIDs when it creates objects in the destination FPOS. However, the tool correctly matches the objects and, depending on the mode in which you are running, takes one of the following actions:
|
Description | Represents record objects that contain the metadata for documents or other objects tracked by Records Manager. |
Deployment Mechanism | Use the Records Manager Transfer tool to move records from a source FPOS to a destination FPOS. This tool also moves the record content to the destination Records Object Store (ROS). |
Dependencies | You must deploy the related Category, Folder, and Schedule objects for the records before you move the record objects. If these objects do not exist in the destination environment when you move the record objects, the Records Manager Transfer tool places the records in a default folder. If the records are placed in the default folder, they lose their schedule information. |
Notes | Because record objects represent the actual objects being tracked, you typically do not deploy record objects from the source environment to the destination environment. However, there might be situations in which you want to move records. For example, you might want to move records from your development environment to your test environment to facilitate testing. The Records Manager Transfer tool is intended to meet DoD requirements, which do not support all records fields and have limited schedule information. As a result, when you use this tool to move a record, some information about the record is lost. For example, if the record has begun disposition, not all disposition information is moved. |