Whether the panel is collapsed (icon-only strip in full-width mode)
Whether the form is in edit mode (panel hides during edit)
Emitted for navigation to a related 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.
The entity record currently displayed in the form
Root-level related IS-A entities to display cards for (children nested inside)
StaticɵdirStaticɵfacThe current record's display name (to suppress in child cards when identical)
Whether there are any related IS-A items to show
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
The shared primary key for all IS-A related records
A callback method that is invoked immediately after the default change detector has checked data-bound properties if at least one has changed, and before the view and content children are checked.
The changed properties.
A callback method that performs custom clean-up, invoked immediately before a directive, pipe, or service instance is destroyed.
A callback method that is invoked immediately after the default change detector has checked the directive's data-bound properties for the first time, and before any of the view or content children have been checked. It is invoked only once when the directive is instantiated.
Relay navigation events from child cards
Container panel that discovers and displays IS-A related entity records (siblings and children) for the current form's record.
Placement: Sits to the right of the main form panels inside
<mj-record-form-container>. Hidden when in edit mode or when no related IS-A records exist.Data flow:
Record(BaseEntity) as inputEntityInfo.ParentEntityInfoandISAChildrento discover related records<mj-isa-related-card>for each root-level related entity (grandchildren render as nested sub-cards inside their parent card)Example