Member Junction
    Preparing search index...

    Runtime renderer for Query dashboard parts. Displays query results using mj-query-viewer with parameter controls and auto-refresh support.

    Hierarchy (View Summary)

    Implements

    • AfterViewInit
    • OnDestroy
    Index

    Constructors

    Properties

    cdr: ChangeDetectorRef
    ConfigureRequested: EventEmitter<PartConfigureEvent> = ...

    Emitted when user clicks configure button

    DataChanged: EventEmitter<PartDataChangeEvent> = ...

    Emitted when the part's data changes (e.g., selection in a grid)

    ErrorMessage: string | null = null

    Error message if the part failed to load

    HasActiveSelection: boolean = false

    True after a wired event of this part fired with a value, until the selection is cleared.

    HasQuery: boolean = false
    InputResolution: PartInputResolution | null = null

    The part's inputs as last worked out from its mappings. Null when it has no mappings: it runs as before.

    IsLoading: boolean = false

    Whether the part is currently loading

    MappedParameters: QueryParameterValues | null = null

    Parameter values from the part's input mappings. They override the user's saved values, are never saved back into them, and show read-only. Null when the part has no mappings.

    NavigationRequested: EventEmitter<DashboardNavRequestEvent> = ...

    Emitted when the part requests navigation to another resource. Parent component handles actual routing based on the request type.

    PartEvent: EventEmitter<DashboardPartEventArgs> = ...

    Emitted when the part raises one of the events it declares (a View part's RecordSelected, a Query part's RowSelected, a component's declared events). Values null: the selection was cleared.

    PartType: MJDashboardPartTypeEntity | null = null

    The part type metadata

    Provider: IMetadataProvider | null

    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.

    QueryId: string | null = null
    RemoveRequested: EventEmitter<PartRemoveEvent> = ...

    Emitted when user clicks remove button

    ShowToolbar: boolean = true
    WiredEvents: string[] | null = null

    The events of this part a dashboard wire listens to. After one fires, the part offers Clear selection.

    "ɵdir": unknown
    "ɵfac": ɵɵFactoryDeclaration<BaseAngularComponent, never>

    Accessors

    • get ProviderToUse(): IMetadataProvider

      Returns either the default Metadata provider or the one specified in the Provider property, if it was specified

      Returns IMetadataProvider

    • get RunQueryToUse(): IRunQueryProvider

      Returns either the default RunQuery provider or the one specified in the Provider property, if it was specified

      Returns IRunQueryProvider

    • get RunViewToUse(): IRunViewProvider

      Returns either the default RunView provider or the one specified in the Provider property, if it was specified

      Returns IRunViewProvider

    Methods