Use ComponentEvent.
The same emitter under the old binding name, so a template still binding (componentEvent) keeps working. Must stay AFTER ComponentEvent: class fields initialise in order, and the other way round this captures undefined.
Controls verbose logging for component lifecycle and operations. Note: This does NOT control which React build (dev/prod) is loaded. To control React builds, use ReactDebugConfig.setDebugMode() at app startup.
Use Initialized.
The same emitter under the old binding name, so a template still binding (initialized) keeps working. Must stay AFTER Initialized: class fields initialise in order, and the other way round this captures undefined.
Emitted once after the component successfully loads and resolvedComponentSpec is populated.
Use OpenEntityRecord.
The same emitter under the old binding name, so a template still binding (openEntityRecord) keeps working. Must stay AFTER OpenEntityRecord: class fields initialise in order, and the other way round this captures undefined.
When true (default), the host transparently persists savedUserSettings
per-user, cross-device via UserInfoEngine — seeding the component from
storage on load and saving (debounced) on every onSaveUserSettings call,
auto-scoped per component. Set to false to opt out and own persistence
yourself by handling the userSettingsChanged output instead.
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.
Use RefreshData.
The same emitter under the old binding name, so a template still binding (refreshData) keeps working. Must stay AFTER RefreshData: class fields initialise in order, and the other way round this captures undefined.
Public property containing the fully resolved component specification. This includes all external code fetched from registries, allowing consumers to inspect the complete resolved specification including dependencies. Only populated after successful component initialization.
Use StateChange.
The same emitter under the old binding name, so a template still binding (stateChange) keeps working. Must stay AFTER StateChange: class fields initialise in order, and the other way round this captures undefined.
Use UserSettingsChanged.
The same emitter under the old binding name, so a template still binding (userSettingsChanged) keeps working. Must stay AFTER UserSettingsChanged: class fields initialise in order, and the other way round this captures undefined.
OptionalUserOptional explicit scope for per-user settings persistence. When omitted, the
scope defaults to <namespace>/<name> of the component spec. Settings are
stored per-user via UserInfoEngine under the key
InteractiveComponents_UserState_Root/<scope>. Provide an
explicit scope when a single component spec is rendered in multiple distinct
contexts that should NOT share preferences (e.g. the same form spec used for
different entities) — set it to something stable and unique per context.
StaticɵdirStaticɵfacUse Component.
The component specification to render. When this changes after initialization, the component will be reinitialized to load and render the new specification.
Use ComponentProps.
Use Container.
Use EnableLogging.
Use HasError.
Use IsInitialized.
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
Use SavedUserSettings.
Use Styles.
Use UseComponentManager.
Sets focus to a specific element within the component
Optionaltarget: string | HTMLElementElement selector or element reference
Gets the current data state of the component. Tries the component's explicit implementation first, then falls back to a DataSnapshot built from intercepted RunView/RunQuery results.
Gets the current data state from the hosted React component. Falls back to a DataSnapshot built from intercepted RunView/RunQuery results when the component does not explicitly implement getCurrentDataState.
Checks if a method is available on the component
Name of the method to check
true if the method exists
Invokes a custom method on the component
Name of the method to invoke
Arguments to pass to the method
The result of the method call, or undefined if method doesn't exist
Use IsDirty.
Checks if the component has unsaved changes
true if dirty, false otherwise
A callback method that is invoked immediately after Angular has completed initialization of a component's view. It is invoked only once when the view is instantiated.
A callback method that performs custom clean-up, invoked immediately before a directive, pipe, or service instance is destroyed.
Use Print.
Print the component content Uses component's print method if available, otherwise uses window.print()
Use Refresh.
Refreshes the component: calls the component's own refresh() when it registered one, otherwise re-renders it.
Hosts that drive a component from outside (an agent operating it through a realtime channel) use this; a
component that manages its own data does not need it.
Use Reset.
Resets the component to its initial state
Use ScrollTo.
Scrolls to a specific element or position within the component
Element selector, element reference, or scroll options
Applies a data state snapshot to the hosted React component. Returns true if the snapshot was successfully applied, false if the component does not support setDataState or the operation failed.
Validates the current state of the component
true if valid, false or validation errors otherwise
StaticforceUse ForceClearRegistries.
StaticForceForce clear component registries Used by Component Studio for fresh loads This is a static method that can be called without a component instance
Angular component that hosts React components with proper memory management. This component provides a bridge between Angular and React, allowing React components to be used seamlessly within Angular applications.