Wiki Detay | wiki workcube

Attention: Standard and custom menus are set by system administrators. Contact the system administrator for applications and information that you cannot access or should not see.

Module Authorizations

Path: Control Panel > Settings > Security > Authorization Groups

Workcube job functions Grouped under Solutions > Job Families > Modules. Module authority determines which modules a user will access and is set under authority groups. Users (roles) included in each authorization group can access the modules authorized in that authorization group. A user who is not authorized to the module cannot access the business functions of that module.

Power user authority is set for each module. An authorization group user with Power User authority can make parameters, data conversions, language settings, first level screen arrangements of that module.

WO - Workcube Objects Job Functions Authorizations

Path: Control Panel > Setting > Security > Authorization Groups

Workcube job functions mostly consist of more than one screen. For example, the Order business function is a WO. A WO often has multiple event screens such as new registration, list and update. The specific powers to be granted to a WO are determined under the "Authority Group". View, add, update and delete permissions can be given for WO.

If the not viewable checkbox is selected for WO, this WO will not appear in the menu. Even if the URL address is typed in the browser, the page is blocked. The user is warned as "Unauthorized Access Request" and the action is logged. The update authority regulates the "Update" button, the add authority regulates the "Add-Save" buttons, and the delete authority regulates the "Delete Record" buttons.

Role Based Page. Authorizations

Path: Control Panel > Setting > Security > Employee Authorization Restricted Pages

In Workcube, a user can be given special authority as an exception from the authorization group. By selecting an employee, a page restriction can be given on the employee's position. For example, special authorizations such as the authority to only record orders and view offers can be issued in the sales module.

Registration Exceptions and Authorizations

This is also an issue related to some operations in Workcube. It is a restriction that prevents two or more people from entering the details of the same form at the same time in some places in the system. This prevents data loss when different people make changes to the same detailed information.

For example, one of the screens where this restriction is applied is the person detail screen. If two personnel users could enter this screen to make changes to different information of the same person, in this case, only the information entered by the last registered person would be processed into the database, thus causing data loss to the other employee who thought he was doing his job. In the current situation, when one of the staff members enters this screen and the other tries to enter the same screen, he/she will be warned that this page is used by the other user and will be prevented from entering the screen.

Branch Authorization - Special Code Authorization

People in the operation can only take action regarding the branches defined for them. As many branch authorities as desired can be defined for a person based on the position details. But if a special code is defined in the system, this authority is restricted. For example, if a personnel officer is authorized to perform transactions in a branch, but at the same time a special code for the driver position is defined for him, that person can only see and perform transactions with the drivers in that branch.

Period – Company Authority

This authorization allows the person given to perform transactions only in selected accounting periods. In addition, there is a date restriction here, and if such a date restriction is set, then the person can only take action after that date during the period he is authorized.

Process Transaction Authorization

Process management allows the records made in Workcube to be managed within certain authority or authority groups. The registration required to be made with a process defined on a specific form follows the process stages and performs dynamically defined operations at each stage. Process authorizations are based on group architecture. You can define more than one authority group during the process stages and assign predetermined positions to these authority groups. Thus, a position can be authorized in one or more stages of one or more processes.

The process triggered by the user warns the next user who is authorized in the stages. It sends informative alerts to the positions defined within the groups. As an example of process management, we can give a product registration process. For example, you can authorize one person to save only the basic information for the product, another to save only the accounting code, and another to activate the product. And these authorizations can be defined in an order that cannot be passed to the other before one is completed.

One of the most important authorization examples in Workcube is this process authorization. Your authorizations are determined from the moment you log in to Workcube. Transactions can be made within the limits of these powers during the usage period. Some of these authorizations are kept in memory and some in the database. Accordingly, your every move is sometimes controlled immediately, sometimes even as you enter, and boundaries are drawn accordingly. For example, the menus you see when you log in are specific to you and you can only see the titles within your authority. Sometimes, when you try to access a page, a message appears warning you that you do not have authorization. This is a control result at that moment.

Feedback

Did you find this content helpful?

2 3

Please Write Your Feedback!

Name*

Last Name*

Email *