The user clicked the built-in close affordance (slide-in wrapper handles it).
Re-emitted from the list — the routine's dedicated conversation was requested.
Loaded/filtered counts changed in the list view.
Routine being edited (null = creating a new one).
Routine whose history is open.
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.
Search text applied to the list view (hosts with their own chrome bind this).
The selected routine (history view) changed — null when returning to the list.
Hosts using query-param round trips two-way bind [(SelectedRoutineID)].
Show a close (X) affordance in the built-in header (used by the slide-in wrapper).
Render the built-in compact header (mark + tabs + list controls). Hosts with their own chrome set false.
Status filter applied to the list view.
The active internal view changed ('list' | 'editor' | 'history').
StaticɵdirStaticɵfacReturns 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 RunReport 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
Deep-link style selection: setting a routine ID opens its history view (clearing it returns to the list). Used by Explorer's query-param round trip.
Force-refreshes the active view's data.
User Routines "command center" — the composite surface combining the routines list (default view), the create/edit form, and per-routine run history behind an internal tabbed navigation. This is the component hosts embed (Explorer full page, the slide-in, or any custom app); the individual pieces remain exported for bespoke layouts.
All child events bubble here unchanged (including the cancelable Before/After pairs), so a consumer only ever wires this one component.