> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/komponenty-rozszerzone/frontendcomponent.md).
# FrontendComponent
{% hint style="info" %}
Availability of functionality depends on the license and may not be available in all deployments.
{% endhint %}
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
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/komponenty-rozszerzone/frontendcomponent.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.