SmartHCM Release Notes 4.1.4.0 MP29

SmartHCM 4.1.4.0 MP29 Release

Release Date: 03-May-2024

Module Version: 4.1.4.0 MP29

Maturity Status: QA Approved

Compatibility

Application	Version
SmartESS MP29	3.1.4.0
SmartHCM Flutter Mobile App. (Android)	2.1.0.0
SmartHCM Flutter Mobile App. (iOS)	1.0.3.0
SmartHCM e-Recruitment	2.1.1.0
SmartHCM Webservice	2.3.6.0
SmartHCM Attendance Uploading Utility	1.1.5.0
SmartHCM Notification Sender Utility	1.0.1.0
SmartHCM WebAPI	1.0.1.0

Enhancements

Introducing Two Factor Authentication (2FA)

We're thrilled to announce the addition of Two Factor Authentication (2FA) to our application, enhancing security measures for our users. 2FA requires the presentation of two distinct forms of identification before granting access, ensuring robust protection against unauthorized access.

Key Features:

Dual Authentication: Users need to provide both a traditional "Password" and a "One-Time OTP Code" for access.

Multi-Channel Delivery: "OTP Codes" can be received either via "Email" notification to the registered "Email Address" or through "SMS" on a registered "Cell Phone".

New Parameters in System Defaults:

To facilitate the implementation of 2FA, we've introduced new parameters in the System Defaults screen.

   Enable/Disable Feature: Admins can now control the activation of 2FA for SmartHCM, SmartESS, and the Mobile App, providing flexibility in its application.

   OTP Code Customization: Admins have the ability to configure parameters such as Length, Expiry, and Regeneration intervals for OTP Codes, tailoring security settings to meet organizational requirements.

New Notification Type: Login OTP Notification

In conjunction with 2FA, we've added a new Notification Type, "Login OTP Notification," to the Notification Calendar screen. This notification keeps users informed about OTPs sent during the login process.

Implementation Details:

   Accessible on Login Screens: The 2FA feature is seamlessly integrated into the login screens of both SmartHCM and SmartESS applications, enhancing security without disrupting user experience.

How to Get Started:

Admins can navigate to the System Defaults screen to configure 2FA parameters according to organizational needs. Ensure all users are informed about this new security measure and guide them through the setup process.

Note:

   Admins are encouraged to familiarize themselves with the new parameters and configure them appropriately to maximize security.

   Users should be educated on the importance of 2FA and guided through the setup process to ensure a smooth transition.

We're committed to providing cutting-edge security features to safeguard your data. Embrace the added layer of protection with Two Factor Authentication (2FA) and fortify your accounts today!

• HRS_S034 - Leave Request: When applying multiple leaves consecutively on the same day, users can use the next leave from the previous one's end time.

Fixed Issues

• PAY_S020 - Payroll Process : When a single code was present while calculating a salary by running a payroll process and the "DURING_MONTH_INCREMENT_OVERTIME_CALC" parameter was set to "Y" in the system default, then overtime was not calculated correctly.

• PAY_R004 - Salary Sheet: The report 'PAY_R041' with an additional column was not working and gave an error.

• PAY_R022 - Pay-Slip : When the report was opened (both PDF and Crystal), the company name should be visible at the top.

• PAY_R038 - Detail Payslip : When the report was opened (both PDF and Crystal), the company name should be visible at the top.

• PAY_S050 - Employee Monthly Payroll Remarks : The Remarks field had the option of an editor/viewer to store multiline remarks.

• HRS_S101 - Appraisal Result Process : When the user ran the final Appraisal result process.

• TOM_R001 - Daily Attendance Report : Proper spacing was ensured between the logo and the company name in the daily attendance report.

• HRS_R032 - Training Course Recommendation : When a user clicked on the "Show Report" and "Show PDF" options, the data of the report was shown in descending order.

• TOM_S036 - Monthly Time Sheet Approval : If a suggestion was pending, a restriction had been set on the approval of the timesheet to ensure that supervisors did not approve timesheets in the absence of overtime suggestions.

• HRS_S117 - Full and Final Settlement : After the authorization of a separated employee, the "Calculate" button on the full and final settlement screen was supposed to be enabled to initiate the process. Upon clicking the "Calculate" button, the attendance was expected to reflect on the employee's payroll attendance.