For the complete documentation index, see llms.txt. This page is also available as Markdown.
Wiring a service at the page or entire application level
Example of attaching a service
In addition to the standard attaching of services to individual components, Eximee allows defining services at the page or request level. They are used to populate multiple fields at once or to perform operations on request entry/exit. For example, you can define a service PageService for a page with the customer's address, which, after entering the postal code, will automatically fetch and fill in the city and province in other fields. Another case is EntryService triggered when the request is opened—for example, retrieving the customer's basic data and filling the form with it.
Step-by-step configuration:
Adding a service at the form level: First, register the appropriate service in the context of the request:
Page service (PageService): To add a page service, open the tab Page services located on the left side of the editor view.
Request entry/exit service (Entry/Exit Service): In the Properties for the entire request, add the service as Entry service (performed when the request is opened) or Exit service (performed when the request is completed or submitted).
Figure 1. Selection window for the service defined for the page (a filtered list of PageService services available on the request)
Attaching a service to a component: Next, select the component that is to display data coming from the selected service (e.g. the Customer City field). In its properties, in the section Interactions, you need to use the field again External data source – click Select a service and search the list for the previously created service. Then select the appropriate Page or Entry service from the list.
Figure 2. Selection window for the output parameter of the service
Mapping results: After selecting the service, go to the tab Output parameters. From the data returned by the service, select the appropriate output field and map it to the component attribute. For example, the PobierzDaneKlientaService service can be mapped so that the attribute value of the City field receives the value from the clientCity parameter returned by the service.
Input parameters (if required): If a page/request-level service requires input parameters (e.g. postal code as input to PageService), these parameters should be bound in the EDS input configuration. By default, listening will be set up for the components indicated in the input parameters.
Refreshing data on change: Thanks to the listening mechanism, if the value in the service's input field (e.g. postal code) changes, the associated Page/Entry service will be automatically called again, and the dependent components will be refreshed. The user does not need to take any additional action—the form will keep the data up to date on its own.
