Difference between revisions of "SmartESS Release Notes 3.0.9.0 MP26.1"
Jump to navigation
Jump to search
Bilal.saeed (talk | contribs) |
Bilal.saeed (talk | contribs) |
||
Line 1: | Line 1: | ||
+ | |||
+ | == SmartESS 4.0.9.0 MP26 Release == | ||
+ | <u>'''Release Date'''</u>: 07-Sep-2023 | ||
+ | |||
+ | <u>'''Module Version'''</u>: 4.0.9.0 MP26 | ||
+ | |||
+ | <u>'''Maturity Status'''</u>: QA Approved | ||
+ | |||
+ | == Compatibility == | ||
+ | {| class="wikitable" border="0" | ||
+ | |- | ||
+ | ! Application | ||
+ | ! Version | ||
+ | |- | ||
+ | | SmartHCM MP26.1 | ||
+ | | 4.0.9.0 | ||
+ | |- | ||
+ | | SmartHCM Flutter Mobile App. (Android) | ||
+ | | 2.0.3.0 | ||
+ | |- | ||
+ | |} | ||
== Fixed Issues == | == Fixed Issues == |
Revision as of 06:07, 7 September 2023
SmartESS 4.0.9.0 MP26 Release
Release Date: 07-Sep-2023
Module Version: 4.0.9.0 MP26
Maturity Status: QA Approved
Compatibility
Application | Version |
---|---|
SmartHCM MP26.1 | 4.0.9.0 |
SmartHCM Flutter Mobile App. (Android) | 2.0.3.0 |
Fixed Issues
- Default.apx - Dashboard: On logging the ESS, error was coming.
- ManageRequest.aspx - Manage Request: "Numeric" field was accepting non integer values; required restriction of text on "Numeric" field.
- ManageRequest.aspx - Manage Request: On forward or approve of any request and if we set any field mandatory in the HCM screen "Request Field setup" of column "mandatory" and "forward, approve" in the column "Input On" then when on forwarding or approving any request when screen to edit request fields got open these fields were showing 'mandatory' blank which was correct but without filling these mandatory fields on click on forward or approve button request was forwarding and approving which was wrong.
- List of Tickets Detail - List of Ticket Detail / تفاصيل التذكرة: "Close Ticket" functionality was not working.
- GenerateRequest.aspx - Generate Request: Wrong attachments were attached in the generated request. Scenario: when we generate any request without any attachments then in the "manage request" screen request was showing attachment in the request which was wrong.