A reusable OmniScript can be nested within another reusable OmniScript, allowing distributed and scalable script development.

A reusable OmniScript can be nested within another reusable OmniScript, allowing distributed and scalable script development.

• A. True
• B. False
• C. Only in Sandbox
• D. Requires special licensing

Answer: (B)

Modular reuse in OmniScript is about building standalone reusable blocks you can invoke from other scripts to avoid duplication and keep maintenance simple. While you can call reusable OmniScripts from a top-level OmniScript to compose functionality, you cannot nest a reusable OmniScript inside another reusable OmniScript. The data context and input/output contracts for a reusable block are defined for a single invocation, and the tooling doesn’t support layering one reusable inside another. The recommended approach for scalable development is to assemble multiple reusable OmniScripts from a single, non-reusable orchestrating script (or from a top-level script) and pass data between them, keeping each reusable unit focused and independently manageable.

Modular reuse in OmniScript is about building standalone reusable blocks you can invoke from other scripts to avoid duplication and keep maintenance simple. While you can call reusable OmniScripts from a top-level OmniScript to compose functionality, you cannot nest a reusable OmniScript inside another reusable OmniScript. The data context and input/output contracts for a reusable block are defined for a single invocation, and the tooling doesn’t support layering one reusable inside another. The recommended approach for scalable development is to assemble multiple reusable OmniScripts from a single, non-reusable orchestrating script (or from a top-level script) and pass data between them, keeping each reusable unit focused and independently manageable.