Which types of fields are not available for individual mapping in Relativity Processing?

The types of fields that are not available for individual mapping in Relativity Processing are the processing system fields. Processing system fields are predefined and integral to the Relativity Processing system, which means they are necessary for the functioning of the processing workflow. These fields include essential data elements that are automatically captured during the ingestion and processing of documents, such as metadata related to the processing state, author, and date of processing.

Since processing system fields are designed to maintain consistency and reliability within the processing lifecycle, they cannot be modified or individually mapped like user-defined fields or custom metadata fields, which can be tailored to meet specific project requirements. User-defined fields and custom metadata fields allow for flexibility and can be configured according to user needs, enabling individual mapping to ensure that relevant data is captured as needed for case management. Document-level fields, which pertain to specific documents rather than the processing workflow itself, can also be mapped individually to support more detailed analysis.

Thus, processing system fields stand out as the only type of field that is not available for individual mapping in the context of Relativity Processing, emphasizing the structured and standardized nature of these essential processing components.