getRichClientApi()

The accessor is cached: every repeated call returns the same instance (identity via ===). The handle methods read the bridge per call (lazily) — a bridge state that is injected or swapped later becomes visible immediately, not only after a new handle.

null and '' are strictly distinct: null means "not readable" (absent member, a throwing call, unknown slot), '' is a real empty value. To tell apart whether the member itself is absent, use rich.has('osjxGetEnvironment'); the facade getSelectedObjects() delivers the normalized selection shape.

rich.call('osjxGetEnvironment', [3]) invokes any osjx* member with the argument array and returns the raw value (or undefined). A missing member throws the descriptive TypeError (see Errors); a throwing bridge call is converted into the descriptive Error. The cataloged methods (table above) are the preferred path — call is the documented fallback for uncataloged endpoints.

The detection semantics are unchanged: a reduced COM-OpenBrowser bridge (only osjxGetBrowserEnvironment + osjxSetBrowserCaption, without the dashlet marker member osjxGetSelectedObjects) is not a dashlet bridge — the environment resolves to standalone, where the accessor throws the wrong-environment error (see Errors). After a richClient resolution (full bridge at detection time), the handle reads the bridge per call; if only a reduced surface shows up at call time, that is reflected honestly: reads yield null, write methods throw the descriptive TypeError, has() returns false for the missing members, and the browser members work.

On client version 10.10, osjxGetEnvironment(n) delivers empty values at start until the warm-up is complete. The handle reads the bridge live — a getEnvironment(…) call before the warm-up ends therefore yields '' (the real empty value), and the value afterwards. The library itself runs its own bounded warm-up with a refresh and re-emission of the context (see environments — v10.10 warm-up).