Whether the flow editor is in full-screen mode
If specified, this provider will be used for communication and for all metadata purposes. By default, if not provided, the Metadata and RunView classes are used for this and the default GraphQLDataProvider is used which is connected to the same back-end MJAPI instance as the Metadata and RunView classes. If you want to have this component connect to a different MJAPI back-end, create an instance of a ProviderBase sub-class like GraphQLDataProvider/etc, and configure it as appropriate to connect to the MJAPI back-end you want to use, and then pass it in here.
StaticɵdirStaticɵfacSurfaces the canvas's dirty state to the host, so the form's Save reflects flow edits.
Returns either the default Metadata provider or the one specified in the Provider property, if it was specified
Returns either the default RunQuery provider or the one specified in the Provider property, if it was specified
Returns either the default RunView provider or the one specified in the Provider property, if it was specified
Queues the flow's steps and paths onto the form's transaction.
Queued rather than saved: the host submits, so the agent row and its flow land together or not at all. Returns true when there is nothing to contribute — an untouched canvas must not block the record's save.
Optionaldecimals: numberOptionalcurrency: stringOptionaldecimals: numberOptionalcurrency: stringClears the canvas's dirty state once the form's transaction actually committed.
Form section component for Flow Agent types.
Wraps
FlowAgentEditorComponentand — via ContributeToSave — makes the flow part of the agent record's own atomic save. The editor's own Save button stays hidden here (ShowSaveControlsdefaults to false): the form owns this record, and two save buttons for one record is how a user ends up with an agent that reports "saved" while their step edits are gone.