In the UiPath Document OCR activity you have an option Use a File Resource click on that, you will be able to give the file path and use the below syntax.
to answer your questions directly, when UiPath Document OCR is nested inside Digitize Document as the OCR engine, it shouldnt ask for a manual Image input at all, Digitize Document handles passing the document internally through its own Document Path property. The fact that Image is showing up as a mandatory field is usually a sign the activity isnt binding correctly to its parent scope, wich points more towards a package issue than something you’re doing wrong
given you are on PDF Activities 4.4.0-preview and IntelligentOCR 7.4.0-preview together, id treat that as the first suspect. Preview packages arent always tested against each other’s exact version, and a mismatch between them is a common cause of an activity’s internal scope resolution breaking like this, wich would explain the “asking for image manually” symptom exactly
to isolate it, id do what you already asked in your third question, downgrade both to the latest stable pair (PDF 4.3.0 and IntelligentOCR 7.3.0) and test the same workflow. If Image stops showing up as required there, that confirms its a preview package compatibility issue and not your workflow logic, and you can report it as a bug against the preview builds specifically
and no, you shouldnt need to convert pdf pages to images first, Digitize Document with an OCR engine attached is built to handle that conversion internally, so if it keeps asking for Image even on stable versions, that would be the real signal something’s off in how the activity was added to the sequence, might be worth deleting and re adding UiPath Document OCR as a fresh child activity instead of reusing the one thats acting up.
