workspaceActionLaunchSelection

This reference describes the full structure of workspaceActionLaunchSelection. Paths include nested objects, list items and conditional branches. A branch selected by kind, contract or mode only admits its own properties.

Structure and values

Field	Options / expected values	Description
contract	"WorkspaceActionLaunchSelection@1"	Required. Exact discriminant of this contract variant. Match the literal value shown.
formFieldKey	string; min length 1; max length 120; /^[a-z][a-z0-9-]*$/u	Required. Key of a declared Field on the relevant type; its value type must be compatible with this use.
flowInputKey	string; min length 1; max length 120; /^[a-z][a-z0-9-]*$/u; optional	Optional. Stable key reference to the corresponding named declaration; the compiler checks existence and compatibility.

Reading the contract

A path ending in [] describes each list item; {key} describes each dictionary value. The ↻ marker refers to the same recursive expression. Closed objects reject additional properties. Semantic validation denotes an additional check: matching a type does not make a reference, permission or transition valid. References must resolve in the Model and the current user context.

An older variant cannot accept properties belonging to a newer variant. The compiler checks the version and consistency of the complete Model.

Structural example

This fragment passes the schema for this section. Its business references must be defined in the enclosing Model.

{
  "contract": "WorkspaceActionLaunchSelection@1",
  "formFieldKey": "target"
}

Related references

Complete Model index · Build a Model

Applied examples : Create a record or start work

A Flow Action prepares a quote; a creation Action opens its dedicated Form.

Configuration

Contract object workspaceActionLaunchSelection. Properties and accepted values.

{
  "contract": "WorkspaceActionLaunchSelection@1",
  "formFieldKey": "target"
}

Variation and connection

Fragment placed in actions[]. Properties and accepted values.

{
  "key": "create-client",
  "label": "Create client",
  "targetDefinitionPaths": [],
  "kind": "semantic-command",
  "operationKey": "create-client",
  "formKey": "new-client",
  "ruleKeys": [],
  "contextPolicyKey": null,
  "minimumRole": "member",
  "confirmation": true
}

UI layout example

The illustrative layout below places this configuration in the Clients/Quotes app. Insert each fragment at the stated location, with Field, Query and Action references matching the Model declarations.

1. Target object
2. Proposed change
3. Checks
4. Confirm

SurfaceClients / North StudioExample

workspaceActionLaunchSelectionworkspaceActionLaunchSelection

Clients

MODEL CONTEXTNorth StudioDeclarative configuration

formFieldKey

target

Values above follow the configuration fragment; references resolve in the complete Model.