This explains the classic scenario of how to work with the most frequently used table/form components and link them in a meaningful way. Basically, every GAPTEQ application is based on the interaction of components via Actions & Events.
In this article you can read the following:
Linking components via Actions & Events
1. Linking components via Actions & Events
The Data Grid component is often used to display a large number of data records in tabular form.
If you want to edit a data record or create a new one, we recommend interacting with the Data Form component.
You control the interactions of the components via Events & Actions!
Events describe the respective options of a component
You use the Actions to define the event that should happen when the event is triggered/occurs.
If you want to edit a data record or create a new one, we recommend interacting with the Data Form component.
You control the interactions of the components via Events & Actions!
Events describe the respective options of a component
You use the Actions to define the event that should happen when the event is triggered/occurs.
- The Data Grid component provides a number of events. For example, you can use the “rowClicked” event to specify what should happen when a data record from your table is clicked.
- You now link this event to the desired action (e.g. navigation, open page())
→ I.e. when a data record is clicked from the table, the application should first navigate to a new page.
2. Use of parameters
You create the best workflow by creating a direct interaction between the components - i.e. in our case, the form components are filled with the previously clicked data record that you want to edit (direct transfer of data records).
Note! To enable direct interaction between components and the “transfer” of data records, GAPTEQ works with parameters.
- You can create parameters at any time under the “URL Parameters” tab on the page.
- You first create the parameter on the target page and can then fill it on the source page.