For the complete documentation index, see llms.txt. This page is also available as Markdown.

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 of the same name, which is written in Angular and included in exForms.

Component properties

Eximee Designer property
Attribute name in the 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 its full path (e.g., if FrontendComponent uses a text field with id GesTextField5 located in the same complex component with id GesComplexComponent3, the path to that text field will be: GesComplexComponent3.GesTextField5)

Requiredness check condition

requiredCheckCondition

Condition for recognizing the component as having a value.

The component may have some value, but the condition in requiredCheckCondition ultimately determines its emptiness.

It is worth noting: requiredCondition - require the FrontendComponent's value (requiredness condition)

List of services

serviceProxies

List of services needed to handle the component. ServiceProxy and ScriptService invoked from the component should be placed here.

List of Contents

textContents

List of used text contents. Remember to add these artifacts also in Dependencies of the main request template.

List of translation keys

translations

List of keys that have a value defined in Languages.

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

FrontendComponent does not have vertical padding in the grid, because some components do not have a graphical representation. Spacing is the component's responsibility.

Adding a component to the request

The component is located in the palette of basic components:

The component added to the request looks as follows:

Figure 1. FrontendComponent added to the request

Component configuration

After placing the component on the request, proceed to 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 set the parameterization: input parameters, translation keys, serviceproxy and contents.

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

Last updated

Was this helpful?