Open a value-help picker for a named scope (model G — sdk-valuehelp-scoping-v1.0 SD3/SD19).
The client's LaravelUi5.openValueHelp({ namespace, scope, mode, context }) dispatches this;
{@see Ui5ValueHelpOpenIntentHandler} resolves scope → entity set and yields a valueHelp
result whose view is the shared shape and whose entitySet is the resolved scope.
Distinct from the generic {@see Ui5ArtifactOpenIntent} (which also opens Applications and
Dialogs, where a scope is meaningless): here scope is mandatory — under model G a value
help is never opened without one, so the constructor forbids a null scope (SD19). Authorized by
{@see Ui5ValueHelpOpenIntentAuthorizer} against the picker's own #[Access] (fail-fast UX); the
load-bearing gate is the set's #[Read], enforced at the OData boundary (SD6).
-
namespace — the shared picker shape (a value-help artifact's namespace).
-
scope — the security surface: a server-defined, server-authorized scope name; the server
resolves it to a first-class set. Never a client-authored filter.
-
context — untrusted caller hints (e.g. a partnerId seed); the server never trusts it.
Wire: { "name": "ui5-valuehelp.open", "parameters": { "namespace": "…", "scope": "…", "context": {…} } }
— hydrated new self(...$parameters), so the constructor parameter names MUST stay namespace,
scope, context. (mode is a client dialog concern — not carried here.)