A scenario is too large, with too many modules. Which technique can reduce the number of modules?

Nesting functions within a module's mapping panel is a core optimization technique in Adobe Workfront Fusion. Instead of using separate modules like "Set variable" for each data transformation step (e.g., converting to uppercase, trimming whitespace, replacing characters), these operations can be combined into a single expression. This consolidation of logic directly reduces the number of modules required to achieve the desired data transformation, making the scenario more efficient, easier to read, and less complex to maintain.

B. This method actively increases the module count by adding a "Compose a string" module and a "Text Parser" module, which is the opposite of the stated goal.
C. The "Auto Commit" setting relates to transaction management and data integrity during a scenario run. It has no impact on the number of modules in the scenario's design.

1. Adobe Experience League Documentation - Map items in Adobe Workfront Fusion: This document details the use of the mapping panel, including the application of formulas and functions. It states, "You can use functions to create more complex mappings. For example, you can use the if function to map a value only if a certain condition is met." This principle of embedding logic directly into the mapping is central to the correct answer. (See section: "Map items using functions").

2. Adobe Experience League Documentation - Built-in functions in Adobe Workfront Fusion: This resource provides a comprehensive list of functions that can be used and nested within mapping panels. For example, a transformation that might otherwise take multiple variable-setting modules can be done in one step, such as substring(upper(Name); 1; 10), which combines the upper and substring functions. This directly supports the technique of nesting functions to reduce module count. (See sections: "Text functions," "Date and time functions").

3. Adobe Experience League Documentation - Best practices for creating a scenario in Adobe Workfront Fusion: This guide emphasizes simplicity and efficiency. It advises, "Keep your scenarios as simple as possible. The more modules you have, the more operations your scenario will consume." While not explicitly detailing function nesting, it establishes the foundational principle that reducing module count is a primary goal for optimization, which is achieved by the technique in option A. (See section: "General best practices").