What condition allows field mapping functionality when the Processing application is not installed?

Field mapping functionality in the context of a Processing application refers to the way that fields within data are aligned or transformed to meet the requirements of particular workflows or data standards. This functionality is essential for ensuring that data can be accurately processed and analyzed, especially when the Processing application itself is not available.

Choosing to add an Invariant to the resource pool is significant because Invariants function as a set of rules or conditions that define how the data should be treated in the absence of certain processing tools. They help maintain data integrity by ensuring that the necessary mappings can still be applied based on predefined criteria. This setup allows users to rely on these established mappings, ensuring that data is still effectively aligned even when direct processing capabilities are not available.

In contrast, creating a new Custodian, disabling Logs, or restarting the job does not directly influence the availability or functionality of field mapping in the absence of the Processing application. These actions relate to different aspects of data handling, management, or operational processes within the system but do not inherently provide the field mapping capabilities necessary for data processing.