Bug #19678
FE - React - MLEB Function incorrect mapping and missing status dropdown fields
| Status: | Closed | Start date: | 19 January 2024 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | chok yee fan | % Done: | 100% | |
| Category: | - | Spent time: | - | |
| Target version: | - |
Description
issue
-----
- incorrect mapping web service fields
- missing status dropdown
- incorrect controlId naming
expected
-----
correction the issue
Subtasks
History
#1 Updated by Nityanantan Nityanantan 11 months ago
- Status changed from New to Resolved
- Assignee changed from Nityanantan Nityanantan to Hazimi Muhammad
Nity- fixed mapping and missing status dropdown in MLEB function
#2 Updated by Hazimi Muhammad 11 months ago
- File WhatsApp Image 2024-02-14 at 10.34.52 AM.jpeg added
- Status changed from Resolved to Feedback
- Assignee changed from Hazimi Muhammad to chok yee fan
Need to double confirm for the MLEB System is it systemCode(screenshot) or systemName(existing code).
#3 Updated by chok yee fan 11 months ago
- Assignee changed from chok yee fan to Nityanantan Nityanantan
as per discuss in the meeting, systemCode is for save, systemName is for display. map from the dataEntry ws to base on the systemCode pull systemName for display
#4 Updated by Nityanantan Nityanantan 11 months ago
- Status changed from Feedback to Resolved
- Assignee changed from Nityanantan Nityanantan to Hazimi Muhammad
#5 Updated by Hazimi Muhammad 11 months ago
- Status changed from Resolved to Feedback
- Assignee changed from Hazimi Muhammad to chok yee fan
Issue has been Fixed.
Go to MLEB Function -> click search button -> select the data in the table -> click modify button -> modify the MLEB System form ->
(the "systemName" for display is correct)
Go to MLEB Function -> click search button -> select the data in the table -> click modify button -> modify the MLEB System form -> click save -> inspect and go to network -> select updateAction -> systemCode: "MLEB_COMMON"
(the "systemCode" for save is correct)