Thanks for the notes above, I see
Melissa
wants my input about the "only uploading one document at a time". Does this mean an admin user would be prevented from uploading another document until HTML conversion process is complete? If so, I think we should come up with a solution that allows for multiple simultaneous documents uploads, because it will be common to upload multiple documents, and having to wait for each document to covert before uploading this next (assuming this takes more than 10 seconds) will interrupt the document uploading process.
Jitesh
and
Harsh
, if simultaneous conversions are not possible, couldn't we create some kind of queue system to deal with this. For example, if document A is converting and the admin wants to upload document B while document A is converting, the admin user can upload document B, but will be presented with the message "pending conversion". This indicates the document B has been put into the conversion queue, and will be converted once document A has completed it's conversion. Similar to what you see with download queues in various applications.
Also, two other points:
Shouldn't there be a way for the document conversion state to update without refreshing the page? This is pretty common in other applications.
I think it's important that we come up with a solution that allows us to maintain performance while loading all the Dispute Document detail fields on one page. It will be common for admin users to scan across the entire page of fields, and having to jump back and forth between pages will make this more difficult.
Thanks,
Morgan
Notified 6 people
Jitesh Dhuravala
Hi
Morgan
,
simultaneously conversions are possible, but our point is admin should upload single document at a time by selecting "choose file" after click on start conversion, Document Details screen will be display for filling the details meanwhile he/she can fill details and can save draft. Now if Admin want to upload second document than he/she click on "Upload Document" from main page.
Morgan
, your example of explaining queuing document A and B, it make sense, but please consider below flow for Admin ( based on current wire-frame).
For Document A, Admin will follow step 1 to 4, now he/she want to upload B document even though A is not completed of conversion than also admin can upload Document B, but he/she must be follow step 1 to 4 for document B.
Now document A is " In process" and document B is "pending conversion". Now once document A completed or fail of conversion than document B will start conversion and status will be " In process". this process will be same for C, D, E, F...
Please consider step 1 to 4 for each document, We will implement API to maintain queue for uploading document, once Admin can click on "start Conversion" than request will be send to API for conversion document by separate thread.
Document Flow - 07_26_19.docx
(7.64 KB)
Thanks for the notes above, I see
Also, two other points:
Thanks,
Morgan
simultaneously conversions are possible, but our point is admin should upload single document at a time by selecting "choose file" after click on start conversion, Document Details screen will be display for filling the details meanwhile he/she can fill details and can save draft. Now if Admin want to upload second document than he/she click on "Upload Document" from main page.
Step 1 :
Step 2 :
Step 3 :
Step 4 :
For Document A, Admin will follow step 1 to 4, now he/she want to upload B document even though A is not completed of conversion than also admin can upload Document B, but he/she must be follow step 1 to 4 for document B.
Now document A is " In process" and document B is "pending conversion". Now once document A completed or fail of conversion than document B will start conversion and status will be " In process". this process will be same for C, D, E, F...
Please consider step 1 to 4 for each document, We will implement API to maintain queue for uploading document, once Admin can click on "start Conversion" than request will be send to API for conversion document by separate thread.
I have tried to explain by diagram as below.
Please provide your feedback in this.
Thanks,
Jitesh
Thanks for the detail above. Looks good to me.
Thanks,
Morgan
This looks great to me. I'll verify that any required changes to user stories are made.
Mel