FrontendComponent

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

FrontendComponent is a component to which we pass an artifact with the same name, which is 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 composite component, you must provide the full path to it (for example: if the FrontendComponent uses a text field with id GesTextField5 located in the same composite component with id GesComplexComponent3, then the path to that text field will be: GesComplexComponent3.GesTextField5)
Requirement check condition	requiredCheckCondition	Condition for considering the component as having a value. A component may have some value, but the condition in requiredCheckCondition ultimately determines its emptiness. Note the following: requiredCondition - require a value for the FrontendComponent (requirement condition)
List of services	serviceProxies	List of services needed to support the component. You should include ServiceProxy and ScriptService that are invoked from the component.
List of Contents	textContents	List of text contents used. Remember to also add these artifacts to the Dependencies of the main application template.
List of translation keys	translations	List of keys that have values defined in Languages.

Some standard component properties have been disabled. For example, if you want the component to have its own tooltip, label or editability condition, you must provide that on the frontend/Angular side.

The FrontendComponent does not have vertical paddings set in the grid because some components do not have a graphical representation. Assigning spacing is the responsibility of the component.

Adding a component to the application

The component is located in the base components palette:

When added to the application it looks as follows:

Illustration 1. FrontendComponent added to the application

Component configuration

After placing the component on the form you should proceed to configuration. To do this click the option located in properties Add Frontend Component (in the section FRONTEND COMPONENT CONFIGURATION). Then provide the component name (in the field Enter component name) and set the parameterization: input parameters, translation keys, serviceproxy and contents.

Illustration 2. An example of translation keys added for the FrontendComponent named CorpoComboboxWithValidationOnItemsComponent