Configure Import Agent DoD Record mode - Manage Records - Foundation 24.1 - Foundation 24.1 - Ready - Perceptive Content - external

Manage Records

Platform
Perceptive Content
Product
Manage Records
Release
Foundation 24.1
License

The DoD Record mode creates record categories, record folders, and records using imported content from the local system or the network. For this mode, Import Agent relies on a manifest file. The manifest file contains a list of the XML files Import Agent imports from your system. To import XML files into Perceptive Content as record content, complete the following steps.

  1. Open inserverImp.ini with a text editor. You must modify two different sections of the inserverImp.ini file.
  2. In the General section, for the import.mode setting, enter DOD_RECORD.
  3. In the General section, for the import.directory setting, specify the directory you want Import Agent to monitor.
  4. In the Mode DoD_RECORD section, for the manifest.file.ext setting, enter the file extension you intend to use for the manifest file. The setting’s default extension is manifest.
  5. Use a text editor to list in the manifest file the XML files Import Agent will import. Record pages are created in the order in which the files are listed in the manifest file.
    \\Important\RecordFiles\f_321YX7H_0000013J0000043.xml
    
    \\Important\RecordFiles\r_321YX7H_0000013J000005L_-1_1.xml
    
    \\Important\RecordFiles\r_321YX7H_0000013J000005W_-1_1.xml
    
  6. Save the manifest file in the import directory you specified in the import.directory setting in the General section.
  7. In the Mode DOD_RECORD section, for the dod.file.retry.attempts setting, specify the number of times you want Import Agent to attempt to import a record before considering the import unsuccessful.
    Note: To specify a directory in which Import Agent stores unsuccessful imports, modify the import.failed.directory setting in the General section.
  8. In the Mode DOD_RECORD section, for the dod.file.status.report setting, specify whether you want Import Agent to generate an import status report.
    • 0 = Import Agent does not generate a report.
    • 1 = Import Agent generates a report for unsuccessful imports.
    • 2 = Import Agent generates a report for both successful and unsuccessful imports.
    Note: The default setting is 0.
  9. If you are importing records into Perceptive Content from an external Records Management Application (RMA), complete the following substeps in the Mode DOD_RECORD section.
    1. For the file.plan.name setting, enter the name of the Perceptive Content file plan.
    2. For the record.type.name setting, enter the name of the Perceptive Content record type.
    3. For the record.folder.type.name setting, enter the name of the Perceptive Content record folder type.
  10. If you are importing records into Perceptive Content from an external Records Management Application (RMA), complete the following substeps in the DOD Record Metadata Mapping section.
    1. To map Perceptive Content record properties to organizational defined metadata in the <AdditionalInformation> section of the importing file, specify a valid XML path for field1 through field5.
      field1 = /OrganizationalDefinedFields/invoice/name
      
    2. To map Perceptive Content custom properties associated with the record type to organizational defined metadata in the <AdditionalInformation> section of the importing file, specify a valid XML path for custom.property1.name and custom.property1.value, repeating both the name and the value settings for each custom property associated with the record type.
      custom.property1.name = InvoiceNumber
      
      custom.property1.value = /OrganizationalDefinedFields/invoice/invoice number
      
      custom.property2.name = InvoiceDate
      
      custom.property2.value = /OrganizationalDefinedFields/invoice/invoice date
      
  11. If you are importing records into Perceptive Content from an external Records Management Application (RMA), complete the following substeps in the DOD Folder Metadata Mapping section.
    • To map Perceptive Content custom properties associated with the record folder type to organizational defined metadata in the <AdditionalInformation> section of the importing file, specify a valid XML path for custom.property1.name and custom.property1.value, repeating both the name and the value settings for each custom property associated with the record type.
  12. Close inserverImp.ini.
  13. Restart the Import Agent service for changes in the inserverImp.ini file to take effect.
Import Agent automatically starts importing the content specified in your manifest file.