Component Data Collection

Providing data that has been modified in the interface as a parameter to an action constitutes the Data Collection process. In the data binding process, we ran an action at the beginning of the screen and showed the results of this action in the interface elements. In this learning content, we will examine defining the data in the interface as a parameter to an action.

Let's take the personnel registration screen as an example scenario.

In the previous learning content, we defined the initial action and screen input for this screen. Now let's proceed to the Save button.

Let's set up the user registration structure for the new personnel to be added through the Save button.

1. Select the Save button.
2. Add the Create User action.
3. Make the relevant definitions in the Create User action via Symbol Picker.
4. Then let's create a Select Action to call the ID in the system of the personnel we have registered as a user.
5. Create and name a Select action through the Custom Action panel.
6. Then select the KUser table as the source.
7. Select Id in the Field field.
8. Open the Filter tab and select the Username column.
9. Then select SQL parameter leaving is equal to selected and type Username and click the Create button.
10. Return to the screen and add the action you created under the Save button.
11. For the UserName parameter, select the Input where you entered the Email information.

Now let's create the action that will save the information of the relevant personnel in the personnel table.

12. Add the Save Record system action to the onClick event of the 'Save' button. Select the Personnel table by selecting Smart.
13. Then select the fields in the Personnel table.
14. Select Screen Input for the ID parameter in the Save Record action.
15. Then define the value taken from Screen Input for ID in the Personnel table, the values taken from the relevant component on the screen using Symbol Picker for Personnel Name and Surname, Personnel Department, Title, Email, Photo Personnel number, and the KUser ID returned as a result of the UserID action for KUserID.

Now let's execute the construct that allows to load a new value, i.e. an image, into the Image element.

16. Select Label with Add.
17. Add the PhotoFromGallery action.
18. Then add the SetValueOf action.
19. Select the Image element.
20. Bind the result returned from the PhotoFromGallery action via Symbol Picker.

This scenario we have realized is an example of Component Data Collection. You can perform similar processes for your own applications in your application development adventure with Kuika.