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 MP28 | 3.1.4.0 |
| SmartHCM Flutter Mobile App. (Android) | 2.1.0.0 |
| SmartHCM Flutter Mobile App. (iOS) | 1.0.4.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
- HRS_S034 - Leave Request : When applying multiple leaves consecutively on the same day, users have been unable to start the next leave from the previous one's end time. They have had to wait one minute, resulting in a deduction of few hours as absent.
- SET_S005 - System Default : A new parameter named "PIN_CODE_SETUP" has been provided for two-factor authentication, allowing users to set the PIN code length, expiry, and other parameters on this screen.
- ESS_S001 - Notification Calendar : A new notification type, "Login OTP Notification," has been introduced on this screen. For this type, users have defined notification text for email for sending the PIN code. It has been placed under the "Login" heading in the Notification Type Combo Box, which was previously labeled "Employee."
- Login - Login : When a user has attempted to log in to the application and has filled in the username and password fields, upon clicking the login button, a new field labeled 'Enter OTP' has become visible. The system has sent the OTP to the user via email, and the user has been required to submit the OTP within a defined time interval. If the OTP has been submitted successfully within the allotted time, the system has proceeded with the login process. However, if the OTP has not been received or the time has expired, the user has had the option to regenerate the OTP again.
- SET_S005 - System Default : A new parameter named "TWO_FACTOR_AUTHENTICATION_ENABLE" has been provided on this screen, which has been used to "Enable / Disable" the "Two Factor Authentication" on the applications such as SmartESS, SmartHCM, and Mobile App. The parameter has had values (Y / N). By default, the "N" value has been shown.
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.
