Somya-05-design
commented
1 month ago I will contibute on this
Open Adameddy26 opened 2 months ago
Somya-05-design
commented
1 month ago I will contibute on this
Current behavior
Currently, there is no implementation of the expected functionality related to the 'Status' mapping field, leading to inconsistencies in record processing.
Expected behavior
Records without a status should default to "draft" and be processed accordingly. Records explicitly set to "draft" should be processed and visible on the draft page. Records with an assigned status should require a facility mapping field; otherwise, they should not be processed.(user should be notified about the mandatory field in this case) Users should receive notifications about any records that were not processed due to invalid status values.
Steps to reproduce the issue
Prepare a bulk count CSV file with varying status values. Upload the file using the bulk count upload feature. Observe the behavior of the records based on the provided statuses.
Environment details
App version : v2.1.0 App environment : UAT