Details
Assignee
Ryan TaylorRyan TaylorReporter
Kateryna SenchenkoKateryna SenchenkoPriority
P3Development Team
FolijetRelease
Trillium (R2 2025)TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Ryan Taylor
Ryan TaylorReporter
Kateryna Senchenko
Kateryna SenchenkoPriority
Development Team
Folijet
Release
Trillium (R2 2025)
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created May 12, 2023 at 10:36 AM
Updated March 4, 2025 at 8:42 PM
Purpose: To provide a better error message for invoice not created because of the mapping issues
As a staff person importing files to create invoices
I want a clear error message indicating that an invoice was not created because there are mapping issues
So that I can understand why the import job errored
Scenarios
Scenario 1
The description value in mapping profile used is not referencing the correct tag in the import file. It was {POL_title}; else IMD+050[4-5] and should be {POL_title}; else IMD+F+050+[4-5] as per import file.
Shown error: Unprocessable Entity {"errors":[{"message":"must not be null","type":"1","code":"javax.validation.constraints.NotNull.message","parameters":[{"key":"description","value":"null"}]}]}
Error message should be more user-friendly - TODO: Define how message should look like
Scenario 2
Issue- Invoice not getting processed(due to incomplete date in DTM tag of the invoice) and UI DI logs do not show problematic record in Error status and do no show the problematic record at all in UI with below error received in CloudWatch logs:
java.util.concurrent.CompletionException: org.folio.processing.exceptions.MappingException: java.time.format.DateTimeParseException: Text ' 2023' could not be parsed at index 0
Handle this exceptions and provide clear UI log - TODO: Define how message should look like