Closed ttlenard closed 3 years ago
mariahkannenberg
commented
3 years ago Reach out to Justine or Santrisha. These are the specific users having these problems. Step 1 - Flexion engineers to try to recreate locally. Chris too. Dynamsoft update - Court to help facilitate update.
mariahkannenberg
commented
3 years ago Get TWAIN printer drivers for the two users as next step.
mariahkannenberg
commented
3 years ago @mmarcotte Looking into TWAIN drivers for the two court users
mariahkannenberg
commented
3 years ago Nothing more for Flexion to do on this. Mike waiting until next week when McVicker is back.
mmarcotte
commented
3 years ago
Describe the Bug A clear and concise description of what the bug is. Justine Miles and Santrisha Mapson in the Petitions section are unable to scan into Dawson particularly it continuously spins, and the image does not load.
Shawn Norman checked her laptop, and she can scan in Adobe but having issues scanning into Dawson. She is scanning in Adobe for the interim, but we need assistance with her not able to scan into Dawson. Chris, Tenille, and Mike all attempted to do the workflow, but we do not have the same scanner that Justine does. Here are some of our notes:
Notes from Chris: I get the spinning behavior when using the automatic document feeder (ADF), but not the flatbed option. I get the same behavior on both Chrome and Edge I can scan to Windows and Adobe normally using any method. Developer tools in both types of scanning don’t report any obvious related errors, aside from the fact that using the ADF just hangs after calling dynamsoft.webtwain.initiate.js, and using the flatbed completes normally. It’s possible someone more developer-tool-savvy than me might be able to mine more info. On my home computer (using Chrome), when I click the Change link for the Scanner selection in DAWSON, I get two options: EpsonB3F6F5 (XP-7100 Series) WIA - EpsonB3F6F5 (XP-7100 Series)
Selecting (b) – which is the only option I have on my Court laptop, aside from some weird Kodak scanner I’ve never heard of nor owned – results in not being able to use the ADF to scan into DAWSON.
Selecting (a) – Works just fine.
Conclusion: It looks like there’s potentially an issue with the Windows Imaging Application driver for a given scanner/printer being used when using the ADF in the DAWSON interface?
More thoughts from Mike: Covering bases, Chris and I paired trying to troubleshoot and replicate the Scanning issue. I really don’t think it’s a DAWSON Dynamsoft issue, though we are overdue for upgrading that Software! We were able to replicate the scanning woes if the scanner was prefixed with WIA-, but is for my scanner prefixed with TW- . This would be something to look for with the user who’s experiencing issues scanning. It really sounds like a laptop problem and NOT a DAWSON problem.
I suspect they have had intermittent issues scanning and they have just gone unreported as they have a tedious workaround. Additionally, the move from Webpack to Parcel did create serious issues with scanning that Cody worked to fix. This could be something else related to that. It’s really hard to know why this is happening for users as there isn’t really any feedback in the Console for what is happening — probably because the Dynamsoft application is gobbling up the error messages. I still think it’s advisable that we catch the software up to the latest as part of routine maintenance. And finally, I think we should address the CSP issue that some users are observing. I am not.
Business Impact/Reason for Severity
high
In which environment did you see this bug?
PROD, MIG
Who were you logged in as?
Petitions Clerk
What were you doing when you discovered this bug? (Using the application, demoing, smoke tests, testing other functionality, etc.)
Using the Application
To Reproduce Steps to reproduce the behavior:
Expected Behavior A clear and concise description of what you expected to happen. Should be able to use the feeder to scan
Actual Behavior A clear and concise description of what actually happened. Error message appears when attempting to use the feeder to scan
Screenshots If applicable, add screenshots to help explain your problem.
This is from Justine
Desktop (please complete the following information):
Smartphone (please complete the following information):
Cause of Bug, If Known
Process for Logging a Bug:
Severity Definition:
Critical Defect Blocks entire system's or module’s functionality No workarounds available Testing cannot proceed further without bug being fixed.
High-severity Defect Affects key functionality of an application There's a workaround, but not obvious or easy App behaves in a way that is strongly different from the one stated in the requirements
Medium-severity Defect A minor function does not behave in a way stated in the requirements. Workaround is available and easy
Low-severity Defect Mostly related to an application’s UI Doesn't need a workaround, because it doesn't impact functionality
Definition of Done (Updated 4-14-21)
Product Owner
Engineering