Add required field indication and validation to invoice field mapping profile
CSP Rejection Details
CSP Request Details
CSP Approved
Description
Environment
Potential Workaround
Attachments
defines
Checklist
hideTestRail: Results
Activity

Ann-Marie Breaux April 20, 2021 at 5:02 AM
Tested on Iris bugfest - required fields are working properly

Ann-Marie Breaux April 9, 2021 at 5:48 PM
Hi Tested on folio-snapshot-load and all looks good. One thing that came to mind. If users start to edit the default EDIFACT profiles, they will need to fill in any missing required fields (like vendor) before saving. But that should be totally fine.

Oleksii Kuzminov March 31, 2021 at 8:43 AM
Hi ! I think we don’t need any migration scripts for it. UI validation is also enough for it

Ann-Marie Breaux March 30, 2021 at 6:14 PM
and I was just thinking about whether this would need a migration script. Field mapping profiles for Invoices were not available before Iris, so Honeysuckle libraries will not have any. And this change will be included in Iris, so no migration script needed. Is that right?
Second question: should we also require these fields on the backend, or do you think having it in the UI is enough?
Details
Details
Assignee

Reporter

Purpose: To indicate required fields on the invoice field mapping profile. Since the field mapping profile will always being creating invoices (not updating them), then the invoice and invoice line required fields can also be required in the field mapping profile.
As a staff person working with invoice field mapping profiles
I want to see which fields are required
So that I can ensure that they have a mapping or a default value, so that invoice creation will not fail
Scenarios
Scenario 1
Given Settings/Data import/Field mapping profiles
When the FOLIO record type = Invoice
Then indicate the following fields are required by adding a red asterisk after the field label
Invoice fields
Invoice date
Status
Batch group
Vendor invoice number
Vendor name
Payment method
Currency
Invoice line
Description
Quantity
Sub-total
Scenario 2
Given the required fields on the invoice field mapping profile
When a user tries to save the profile without all required fields being filled with a mapping or default value
And presses the Save button
Then disallow the save, and place the cursor at the first required field that has not been filled in (the same behavior used when Profile name, Incoming record type, or FOLIO record type is not filled in)
Scenario 3
Ensure this story passes Accessibility testing
Scenario 4
Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot