You can provide role-based authorizations to elements and screens in the applications you develop with Kuika.
For example; you can ensure that only users with the admin role can access the employee information editing screen in a web application with authorization.
You can provide role-based authorizations to elements and screens in the applications you develop with Kuika.
For example; you can ensure that only users with the admin role can access the employee information editing screen in a web application with authorization.
To perform the authorization process, you can use the Authorization section through the properties panel while the relevant element and/or screen is selected.
While you can provide Anonymous access to elements and/or screens through the Authorization section, when you turn off Anonymous access, you can provide access to all roles or role-based access.
Now let's look at the authorization processes specific to elements and screens.
During the application development process with Kuika, you can manage authorization processes specific to elements and screens by creating roles.
For example, let's create two users in the role of administrator and employee. To create roles, first click on an element or an empty area on a screen in the application. From the Authorization field opened in the Properties panel, disable the All Roles Access Switch if it is active. Then click the NEW ROLE button under the Roles heading.
Enter the Role name on the Modal screen that opens. After entering the Role name, if you wish, you can optionally specify a start screen for the Role you created. After these operations, you can complete the role creation process by clicking the Create button.
Within the scope of this application, we can create two roles named Employee and Manager.
At this point, it will be useful to underline the following information. The roles you have created are saved in the KRole table from the Kuika system tables in ManageDB. You can use Authorization actions from system actions to associate registered roles with designs in UI Design view mode, that is, to use them in the design or to perform role authorization operations such as assigning user roles. For example, in the process of adding a new employee, you can also carry out the role determination process of the employee you add by using the Add User To Role action.
So how will we carry out the authorization process for elements and screens according to the roles we have created? Let's look at the answer to this question together.
You can manage the viewing/access authorization of the elements in the application according to the user roles. For example, on a List screen in the application, you can make the button that redirects to the new staff addition page visible to users in the administrator role, while you can hide it for users in the employee role.
Providing authorization on screens during an application development process is a critical step to ensure that users have the right level of access to the application and that their privacy is protected.
You can easily authorize the screens you create during the application development process from the Authorization field in the Properties panel. Thus, you can adjust the visibility of the screens according to the roles your users have.
For example, in a employee management application you have developed, you can allow users with the administrator role to access a new employee addition form screen, while you can hide the access of users with the employee role to a new employee addition form screen.
You can provide role-based authorizations to elements and screens in the applications you develop with Kuika.
For example; you can ensure that only users with the admin role can access the employee information editing screen in a web application with authorization.
You can provide role-based authorizations to elements and screens in the applications you develop with Kuika.
For example; you can ensure that only users with the admin role can access the employee information editing screen in a web application with authorization.
To perform the authorization process, you can use the Authorization section through the properties panel while the relevant element and/or screen is selected.
While you can provide Anonymous access to elements and/or screens through the Authorization section, when you turn off Anonymous access, you can provide access to all roles or role-based access.
Now let's look at the authorization processes specific to elements and screens.
During the application development process with Kuika, you can manage authorization processes specific to elements and screens by creating roles.
For example, let's create two users in the role of administrator and employee. To create roles, first click on an element or an empty area on a screen in the application. From the Authorization field opened in the Properties panel, disable the All Roles Access Switch if it is active. Then click the NEW ROLE button under the Roles heading.
Enter the Role name on the Modal screen that opens. After entering the Role name, if you wish, you can optionally specify a start screen for the Role you created. After these operations, you can complete the role creation process by clicking the Create button.
Within the scope of this application, we can create two roles named Employee and Manager.
At this point, it will be useful to underline the following information. The roles you have created are saved in the KRole table from the Kuika system tables in ManageDB. You can use Authorization actions from system actions to associate registered roles with designs in UI Design view mode, that is, to use them in the design or to perform role authorization operations such as assigning user roles. For example, in the process of adding a new employee, you can also carry out the role determination process of the employee you add by using the Add User To Role action.
So how will we carry out the authorization process for elements and screens according to the roles we have created? Let's look at the answer to this question together.
You can manage the viewing/access authorization of the elements in the application according to the user roles. For example, on a List screen in the application, you can make the button that redirects to the new staff addition page visible to users in the administrator role, while you can hide it for users in the employee role.
Providing authorization on screens during an application development process is a critical step to ensure that users have the right level of access to the application and that their privacy is protected.
You can easily authorize the screens you create during the application development process from the Authorization field in the Properties panel. Thus, you can adjust the visibility of the screens according to the roles your users have.
For example, in a employee management application you have developed, you can allow users with the administrator role to access a new employee addition form screen, while you can hide the access of users with the employee role to a new employee addition form screen.
