Wiki Detay | wiki workcube

Workcube's holistic business process management (BPM) philosophy aims to ensure that information reaches the right person at the right time and that the necessary actions are taken without delay. The Employee Alerts and Acknowledgments business function is one of the most proactive tools of this philosophy. It is the central parametric screen where system administrators and HR experts manage critical warnings, surveys, commitments or approval mechanisms that employees will encounter when they first log in to the system. Thanks to the defined rules, when users log in to the system, they instantly see a list of critical alerts that concern them on the home page and are directed to the relevant action page with a single click.

When a user successfully logs in to the system, queries (query codes) running in the background analyze the user's status. If there is an active warning or mandatory approval process defined for the user, the system directs the user directly to the relevant action page (fuseaction) or requires the user to complete the action by opening a modal warning window on his screen. It can work in full integration with all main modules such as HR (KVKK approvals, employee surveys), CRM (pending urgent customer complaints), SCM (critical purchase approvals) and Finance (limit exceedance approvals).

Page Parameters and Definition Fields

There are a few things to consider before defining alerts for employees; When each user logs in to the system, database queries (warning_code) of all active warnings defined on this screen are run one after the other. If the SQL queries written are not optimized, heavily join a large number of tables, or scan unindexed fields, user login times will be significantly longer and unnecessary load will be placed on the server. Provide a maximum of 1 or 2 active mandatory alerts to employees during the same period. Instead of forcing login for temporary announcements or non-urgent surveys, prefer to use Workcube Intranet / Portal widgets. Login warning should only be activated for legal obligations and critical process interruptions.

The following fields are used when adding a new warning rule or editing existing rules in the system:

Warning: This is the main title / warning text that the user will see in the warning box on the home page.
Description: The detail located right below the warning and informing the user what to do.
Code: This is the control SQL query that will run in the background and determine whether the alert will be triggered or not. If the record is returned as a result of the query, the warning will appear on the screen.
Fuseaction:This is the fuseaction code where the user will be directed to take action when he clicks on the warning on the home page.

Sample Scenarios

Scenario 1 (Resume Check): If the employee's CV information is empty in the system, he/she will be directed to the myhome.mycv page and asked to fill out his/her CV.
Scenario 2 (Unupdated Jobs): If the employee has a job whose deadline has passed 72 hours but its status has not been updated. You will be directed to the project.works page and asked to close or update the job status.

Feedback

Did you find this content helpful?

Please Write Your Feedback!

Name*

Last Name*

Email *

About Workcube Objects

Warnings and Approvals for Employees

This is the management screen that allows defining warning messages to be displayed to employees logging in to the system, checking the activation status of these warnings, and arranging target pages so that users can take the relevant action.

Type: Process Version: Adaptive v1 Licence: Standard Author: Workcube Core