Compiled and Invoked Functions
Summary
Runline U can compile, distribute, and invoke workbook-provided functions where those capabilities are enabled.
Core Idea
Compilation creates callable code; invocation executes a named compiled function. Distribution and macro execution widen the security and operational scope.
How It Works
U.COMPILE prepares functions, U.INVOKE calls them synchronously, and async or macro variants change execution behavior. Script functions provide a separate mechanism for sequencing workbook actions.
Why It Matters
Code execution, distribution, and process launch cross a stronger trust boundary than ordinary worksheet transformations.
In Excel (Runline U)
Keep source code, registration settings, invocation inputs, and returned errors visible. Use only approved code and deployment paths, and avoid placing secrets in worksheet source or logs.
Common Patterns
- Compile a focused calculation and invoke it from worksheet formulas.
- Use asynchronous invocation only when the workbook can handle delayed results.
- Distribute functions through the established controlled workflow.
Misconceptions
- A compiled function is not automatically safe because it was created from a workbook.
- Async invocation and macro invocation have different timing and Excel-context implications.