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ɵ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
Closes the dialog without saving. Routes through the setter — the single ShowDialogChange emit path.
Content saved successfully — surface it and close
Opens the dialog (the embedded content component loads on creation). Routes through the setter — the single ShowDialogChange emit path.
Full-screen modal dialog for configuring user's application visibility and order. Thin wrapper: the actual configuration UI (list/reorder/persistence) lives in
mj-user-app-config-content, which the shell's app launcher also embeds directly as an in-panel view. This wrapper only provides the modal chrome + theShowDialog/Open()/Close()API its dialog consumers use (e.g. the Home dashboard).The content component loads its data in ngOnInit — because it is created fresh under this template's
@if (ShowDialog), everyOpen()gets a fresh load with no stale-list flash (the concern bug F1's resetLists() addressed in the pre-split monolith is solved structurally here).