Abstract Subclasses can emit anytime an error occurs.
Subclasses can emit this event anytime they want to communicate with the container to let it know that something has happened of significance.
Subclasses can emit this event anytime they want to open a record within a particular entity. The container should handle this event and open the record.
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.
Subclasses should emit this event anytime their internal state changes in a way that they'd like to persist.
Protected _configPrivate _visibleStatic ɵdirStatic ɵfacSet or change the dashboard configuration. Changing this property will NOT cause the dashboard to reload. Call Refresh() to do that.
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 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
Abstract GetSub-classes can override this to provide a custom icon class
Protected NotifyProtected NotifyProtected ResourceProtected Abstract initProtected Abstract load
Make the base class a directive so we can use Angular functionality and sub-classes can be
Component