Macros and App Building
Macro and app questions separate designers from builders. Three macro types: Standard (reusable workflow with macro inputs/outputs, saved as .yxmc), Batch (iterates over rows or a field, one run per group), and Iterative (loops until a condition, using the Iteration Output/Input). The Interface tools (Text Box, Drop Down, List Box, File Browse, Check Box, Numeric Up/Down, Date, Action) drive Analytic Apps; the Action tool wires a control to a workflow element (update value, update field, update raw XML). Condition and Message tools control flow and validation. The Question tab configures prompts; the Interface Designer previews.
Traps: a Batch macro needs a Control Parameter to pass the group value; forgetting it means every iteration runs identically. Iterative macros need a termination condition or they run forever. Interface elements only affect the workflow through an Action tool - a Drop Down with no Action does nothing. Chained Apps use the Test tool or output to trigger the next app. Apps must be packaged (.yxzp) to include assets.
Worked example: process 50 store files. Build a Batch macro whose Control Parameter receives the file path, with a Dynamic Input reading that path. The outer workflow feeds a list of paths into the macro input. Rule of thumb: No Control Parameter, no batch variation.