UFFI Error log handling
AnsweredCurrently when a UFFI functions in error, the log file gets the error message and is placed in the 'Log + curent date' directory. The incoming error file gets placed in the Error directory. Let's view this from point of view of the clerk that is tasked with checking for import errors (or gets an alert). They look in the 'error' directory. They see several files (XML, JSON, CSV - whatever) and know these are the files that did not get imported. They may be able to look at say a JSON file and see the error or maybe not - depends on their training. They could look at the LOG file and it may say something like 'CardCode' not found or is inactive. But what do they actually 'see' in the log file directory? If the company imports 150 orders per day, they see 150 log files all 'named' with the date and the time. They need to 'pick' the one that matches with the JSON file from the error file directory.
My suggestion is simple: when there is an Error file written to the Error directory, also write the log file associated with this file into the Error directory. That way the user - if there are only 2 or 3 rejected orders, simply needs to open the 2 or 3 log files to see the error. Also write the log file into the 'log' directory for consistency.
Much more user friendly. And the training for the user is vastly simplified.
-
Thank you for your request. It has been scheduled for review by the development team that will get back to you should there be questions.
(Please note that as we are user-driven we can't guarantee that your request will be met unless it gets many votes and/or fit the product vision)
Read more about the Feature Request process here
[Internal Id: 142058]
Please sign in to leave a comment.
Comments
1 comment