Components

Components serve as the building blocks for modules and applications. For example, a component can be a FMM model, user interface, or a dashboard.

This page describes what components are, how they differ from modules and applications, and when to create them.

A Closer Look at Components

To gain a better understanding of components and their relationship with modules and applications, consider the following characteristics:

• Components can contain both backend and UI elements.
• Components can contain multiple types of artifacts, such as FMM models, serverless workflows, solution services functions, and dashboards.
• Components can be used to divide a module into smaller pieces, such as the module's FMM model. This allows other modules and components to define a dependency at a granular level instead of on the entire module.
  • Example: Module A requires the FMM model of module B. If the FMM model is defined as a separate component, module A can define a dependency on only the component rather than on module B as a whole.
• Components can be a dependency for other solutions, but cannot be explicitly subscribed to by a tenant.
• Components are not listed in in the list of subscribed solutions, but are implicitly subscribed to if the tenant subscribes to an application or module that is dependent on the component.