hello All,
I am getting below error in Data Extraction Scope .
Data Extraction Scope: Validation Station can’t be presented: no input file available
Below are the logs -
Please guide!
Thanks !
Hey @Navneetj3
I think the variable you’re passing in document path is not able to get the file check once if it is
taking the file or not
Hi @Parth_Doshi
Before Wait for Document classification Action and Resume i am able to write the file . But after action item gets completed the item is blank .
The file is getting classified properly during wait for document classification action and resume?
yes @Parth_Doshi
@Lahiru.Fernando can you please guide me in this ?
Hi @Navneetj3
Can you show me the screenshot of how you have configured the data extraction scope, and how you have configured the validation station ?
below are screeenshots of the sequence (I am not using validation station for data extraction)
can you run this in debug mode, and once it tries to execute the Data Extraction Scope, can you show me the values you get for the below variables used in data extraction scope:
item
Doctext
dom
taxonomy
classification
Also show me a screenshot of “Configure Extractors” screen
@lahiru thanks for responding below is the screen shot for the values -
screenshot for configure extractors screen-
This was continued in PM, but thought of sharing it here because this conversation might help a lot who come across this situation. This includes how it has to be handled and solved.
Hello @Navneetj3
Was away for a while. Sorry…
I went through your images, and seems like all the variables have the needed values. I wonder whether this is caused by the wait classifier activity on the top.
Can we do a simple check change here to see whether it is actually the cause?
Instead of wait classifier activity here, Can you use the present Classification Station activity to set the classification? Use that data for extract step below and see whether that runs without this error…
This is a wild thought, but may be my guess works… Just try 
1 Reply
Reply
Lahiru.Fernando
okay i am doing the same .
1 Reply
1
Reply
Navneetj3
@Lahiru.Fernando i am able to extract data without wait classifier activity . actually before trying wait classifier i used the normal doc processing flow without integrating action center for classifiers . it was working fine , even working fine now as well .
1 Reply
1
Reply
Navneetj3
Is it a bug or something needs to report ?
1
Reply
Just as I thought,
its not really a bug though. This is what is happening… let me explain,
So, when the process goes into the suspended state, the values in the already available variables may get cleared, so once the process resumes, you will not have the values of those variables you had earlier. All you will have is what returns from the wait activity.
So, taking that into account, the wait activity returns you the taxonomy, classification, object model, and document text. What is missing is the document file path that you can in the “item” variable.
Now, you may run into a confusion here. Studio showed you the item variable value when we debugged earlier.
Yea… though it showed you, it is not valid after resuming. So that’s the problem.
1
Reply
Lahiru.Fernando
yeah ,after resume the item is blank.
1
Reply
How you can solve this is,
You have to break this process into two processes.
First process, have these steps
read the directory
Read Taxonomy
For each loop
inside:
digitize document
Classification scope
have a decision node to decide whether you want to create the task in action center or not to verify classification.
Create a Orchestrator storage, and add the file path that you have in the “item” variable to the storage so you can refer it later
if condition is true,
Invoke another process to handle the task creation, waiting, and resume. (Process 2)
if condition is false,
Invoke process 3 (mentioned below)
– This is all you have in your first process –
Process 2:
This is where you create the task
steps:
Create the task
Wait activity
Once it is resumed, Pass the data you got as output from the wait, to another process
– this is all you have in your process 2 –
Process 3:
This is where you get the data from process 2, and start extracting…
In here
Use the read Orchestrator storage, and retrieve the file path
delete whatever it is stored there so you don’t over use space later at the end
Now have your data extraction scope and rest of the activities here
This way you have handle this
3 Likes
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
Yoichi
Anil_G
AJ_Ask
George_Knott
ppr
gorby
adi.mehare
Daniel_Santos1
alexander.deuschlinger
yangyq10