FrontendComponent

Availability of the functionality depends on the license and may not be available in all implementations.

FrontendComponent is a component to which we pass an artifact of the same name, written in Angular and attached to exForms.

Component properties

Eximee Designer property	Attribute name in Source	Description
Component name	componentName	FrontendComponent name
Component configuration	config	An object containing configuration specific to each FrontendComponent. If the source is located in a complex component, provide the full path to it (e.g., if a FrontendComponent uses a text field with id GesTextField5 located in the same complex component with id GesComplexComponent3, then the path to that text field will be as follows: GesComplexComponent3.GesTextField5)
Required check condition	requiredCheckCondition	Condition for recognizing the component as having a value. A component may have some value, but the condition in requiredCheckCondition ultimately determines its emptiness. It is worth noting: requiredCondition - require the FrontendComponent value (required condition)
List of services	serviceProxies	A list of services needed to handle the component. It should include the ServiceProxy and ScriptService called from the component.
List of Content	textContents	A list of used text contents. Remember to add these artifacts also in the Dependencies of the main application template.
List of translation keys	translations	A list of keys that have a value defined in Languages.

Some standard component properties have been disabled. If, for example, we want the component to have its own tooltip, label, or editability condition, this must be provided on the frontend/Angular side.

The FrontendComponent has no vertical paddings assigned in the grid, because some components do not have a graphical representation. Adding spacing is the responsibility of the component.

Adding a component to the application

The component is located in the base components palette:

Added to the application, it looks as follows:

Figure 1. FrontendComponent added to the application

Component configuration

After placing the component on the application, go to the configuration. To do this, click the option located in the properties Add Frontend Component (in the section FRONTEND COMPONENT CONFIGURATION). Then enter the component name (in the field Enter component name) and define the parameterization: input parameters, translation keys, serviceproxy and content.

Figure 2. Example of translation keys added for a FrontendComponent named CorpoComboboxWithValidationOnItemsComponent