Conditional Expressions in Field Mapping

Summary:
Enable users to apply conditional logic within field mappings so values can be directed to different target fields based on source data conditions. This would allow a single import or export mapping configuration to support multiple business scenarios without requiring separate mapping setups.

Problem Statement:
Current field mapping capabilities do not support conditional expressions that evaluate source data and dynamically determine the correct target field. As a result, users must create and maintain separate mapping configurations for each scenario, which increases setup time, adds complexity, and makes ongoing maintenance more error-prone. This is especially inefficient for teams managing imports or exports with varying contract types, record categories, or other conditional data patterns.

Proposed Solution:
Add support for conditional expressions in field mapping that allow users to define if/then logic within a mapping rule.
Enable mappings to evaluate source field values and route data to different destination fields when specified conditions are met.
Support common business scenarios such as mapping one field when contract type equals T&M and a different field when it does not.
Allow this logic to be configured within a single mapping flow so users do not need to duplicate entire import or export templates.
Ensure the configuration is clear, easy to maintain, and validated to prevent incorrect or conflicting mapping behavior.

Benefits:
Reduces the need to create multiple mapping configurations for similar workflows.
Improves efficiency by allowing more flexible and intelligent field mapping logic.
Simplifies maintenance by consolidating scenario-based rules into one configuration.
Decreases the risk of manual errors caused by duplicated or inconsistent mappings.
Supports more complex real-world data transformation needs within import and export processes.