Symbol Picker plays an important role when developing applications with Kuika.
Symbol Picker is presented in various categories. These categories are Default, Fixed Value, Components, Action Results, Screen Inputs, Method Input, Role List, Report Input, Current.
The Default category contains data types that are provided by Kuika by default and can be used in the application development process.
For example, you can use the value Empty to show an empty field by default in a form.
The data in this category are: Empty, Space, Current Username, Client Ip Address, Version Info and Null.
Let's take the example of an application form for participation in an online seminar. In the form, participants can enter their name, surname and phone number. However, if you do not want to enter your phone number, you can hide this field with the “I don't want to add my phone number” button. In the example, three people named Empty, Null and Space apply for the seminar:
The phone number information of these people is shown in the SQL table below.
The Fixed Value category represents fixed and unchanging values when developing applications with Kuika. It provides fixed data that can be used in various elements on the application screen and makes it possible to bind this data directly within the application.
For example, if you want to show the text “Home” in the Label element, you can specify this value through the Fixed Value category.
The Component category represents the different types of elements on your screen when developing applications with Kuika. It allows you to dynamically link the data provided by various elements in the user interface.
For example, if you use an element from the Input, Date or Special Element category in an application screen, you can find the data provided by these elements under the Components category.
The Action Results category represents the results of the actions you add to your application while developing with Kuika. It allows you to dynamically link the data returned by the actions performed by the actions and allows this data to be used within the application.
For example, if an action is used to collect data from the user, perform a transaction or trigger a specific workflow, the information returned as a result of this action will be in the Action Results category.
The Screen Inputs category contains inputs received from the user on the application screen. You can process data that users provide through forms or other screen elements.
For example, when a user enters an email address in a form, the email address falls under the Screen Input category and can be processed in your application.
The Method Input category represents the input parameters of the methods used in your application. You can manage the data sent to the methods and use this data in the application workflow.
For example, if a method needs to get a user ID, this user ID is included in the Method Input category and is used as a parameter for the method to run.
The Role List category contains the list of roles defined in your application. It helps you manage users' access permissions and workflows based on their roles.
For example, if roles such as “Admin”, “Editor” and “Viewer” are defined in an application, these roles are displayed in the Role List category and can be used for related operations.
The Report Input category represents the input data to be used in your reports. It provides parameters or filters that are required when creating a report.
For example, if a report will use filters such as a date range or a specific group of customers, these filters will be included in the Report Input category.
The Current category represents that data is bound to one of the elements in the Data category.
For example, when data about the Department list is bound to the Table element, it will be in the Current category.