First Draft of the document has been created & attached with JIRA ticket:
EDI-Dashboard.docx

Regards,
Satya Prakash

To be added to the requirements:

Need the system to provide reason of failure under Import/Export > Manual Import/Export page. Currently it just states “Import Failed.” Normally, a JIRA ticket needs to be opened for development to troubleshoot the error.

For both scheduled as well manual import/export, as an immediate measure, we can have the back-end “error log” exposed to the user via error message. As this will be a run-time error, it will have limited use – but it will be better than the current error message. In most cases it would tell the user which macro caused the error. Sharing this message with development will save investigation time as well.

Lalit Kumar and Rakesh Roy - EDI Team had a meeting with Samir and Amit Thorve where we added the following requirement. CC Cindy Wibbing

• When a developer fixes the issue for a failure (like making space on the server, opening a port or a code fix), they should add a note about that against the feed failure. In other words whenever the reason of failure is not trivial (i.e. the file typically gets uploaded when refired, or after updating the credentials) - there should be a comment that states reason of the failure and gives some details of the fix that resulted in succesful file generation/ upload.
• The dashboard should be able to export a simple report that gives information about the failed feeds, just like the report currently mailed by Mandar - with additional information like cause of failure (noted by development or the EDI person), number of attempts and when did it run successfully.
• We need documentation that maps the error message and issues that cause those errors.

Added a file that has mapping of import errors compiled by Monika Demla.