The Namespace property is optional for Visualforce pages in OmniScripts.

The Namespace property is optional for Visualforce pages in OmniScripts.

• A. True
• B. False
• C. Sometimes
• D. Only for mobile

Answer: (B)

Namespace is how OmniScript identifies a Visualforce page that lives inside a managed package. When a Visualforce page is provided from a managed package, you must supply the Namespace prefix so OmniScript can resolve the page correctly (for example, Namespace__PageName). Without the Namespace, OmniScript cannot reliably locate the page and will run into resolution errors. If a Visualforce page has no namespace because it’s created in your own org (not in a package), you can leave it blank, but in general—especially with packaged pages—the Namespace is required. So saying the Namespace property is optional isn’t correct in typical OmniScript use cases.

Namespace is how OmniScript identifies a Visualforce page that lives inside a managed package. When a Visualforce page is provided from a managed package, you must supply the Namespace prefix so OmniScript can resolve the page correctly (for example, Namespace__PageName). Without the Namespace, OmniScript cannot reliably locate the page and will run into resolution errors. If a Visualforce page has no namespace because it’s created in your own org (not in a package), you can leave it blank, but in general—especially with packaged pages—the Namespace is required. So saying the Namespace property is optional isn’t correct in typical OmniScript use cases.