We are using IXP model to extract the data, also we can convert to table from document_out of IXP extraction. when i create task for user to validate, i capture task id. with help of this task id, after user completes the validate how to extract the data from task. Can you some one suggest a good approach.
Create a validation task “Create Document Validation Action” and capture the “TaskId”.
Wait for the user to complete the task using “Wait for Document Validation Action and Resume” activity.
After the workflow resumes, the Document object (DOM) is automatically updated with the user’s corrections.
After the Document object is updated, follow these steps to extract the data and export. Use activities such as Export Extraction Results, Get Extraction Results, Convert Document Data to DataTable. These should be executed after the validation task completes so they extract based on the validated data.
My requirement is IXP will extract the data, i am using Create Validation Task to push to action center, from there business user will validate and make some correction and submit. Next day i need to get the task and convert into excel file
Hi @Abinash_Nagarajan ,
Can you please check with these if possible Create Document Validation Action and Wait for and Resume because maybe the latest version doesn’t contains that activities.
the reason those activities arent showing up is most likely your project’s target framework. “Wait for Document Validation Action and Resume” and the classic validation activities live in the Windows only version of the Document Understanding/IntelligentOCR package, if your project is set to Cross Platform (wich is common for newer Studio projects, specially anything with IXP), that activity wont appear in the panel at all even with the package installed
quick way to check, open Manage Packages, search for UiPath.IntelligentOCR.Activities or UiPath.DocumentUnderstanding.Activities, and look at wich version and whether theres a separate Windows compatible package installed alongside it. If your project.json shows targetFramework as “Portable” or “CrossPlatform” thats your answer
if switching target framework isnt an option for your project, the more future proof route since you’re already on IXP anyway is skipping the legacy Suspend/Resume pattern entirely and pulling the result the next day through the Orchestrator/Action Center API directly using the TaskId you saved, a GET call on the task endpoint returns the completed status and the validated document data as json, wich you can then convert to your table/excel the same way. That also fits your case better since you specifically want to decouple task creation from retrieval by a day rather than keep one workflow suspended waiting
worth double checking exact activity naming for your specific package version too since it shifts between releases, but the target framework mismatch is the first thing id rule out. hope this helps you as well
just tested here to be sure, theres an activity called Get Task Data that seems to do exactly what you want, you pass the TaskId and it fetches the action even if it was created in another workflow, so it fits your next day scenario without api
it comes in UiPath.Persistence.Activities (im on 1.10.1) and sits under Tasks in the activities panel. I checked on both a Windows and a Cross platform project and it shows up in both, so project type shouldnt be a problem for you
one thing im not sure about is how the output will look in your case, it returns a Task object and for document validation actions I’ve read the validated data comes packed inside it rather than as a ready document object. Maybe just log what comes in the output first, that tells you if you can go straight to your excel or if theres unpacking to do
that output actually has what you need, just not the data itself. In the Data section it gives you the bucket and the paths, and the validated results are in ValidatedExtractionResultsPath, that output_results.zip
so next step would be Download Storage File. Just dropped it here to check the properties, it asks for Storage bucket name, so use du_storage_bucket and not the BucketId. File Path is the ValidatedExtractionResultsPath value, and theres a File name and location field for where it lands locally. Since your json shows a FolderPath, you probably need to fill the Orchestrator folder path too or it wont find the bucket
then Extract/Unzip Files on it. One thing to watch, “Extract to dedicated folder” comes checked by default so it creates a subfolder instead of dropping the file straight in your destination. It also has an Extracted Files output that gives you the files directly, easier than guessing the name inside