Hi,
I’m currently building a process using REFramework and running into an issue related to persistence. I have already enabled persistence support but I’m still encountering the same error.
Could anyone help me understand what I might be missing or doing wrong.
Keep in mind, that at least in the past specific persitence related activities can only be used at the XAML which is set as Main
Can you share more details on what other changes you have done along with enabling persistence?
Also, can you share some insight on your use case, because if you want to build a long running process (using persistence), UiPath has Orchestration Process template which is specifically designed for long running automations.
The above mentioned error has been resolved.
Thanks
@aparna.dhanesh Great, please let us know how it resolved so it’ll help others as well
Hi @Rohit_More ,
The above-mentioned error changed after I moved my Wait for Form Task and Resume activity from Process.xaml (Performer) to the Process State of Main.xaml. I’m now getting the following error: The value for argument ‘taskInput’ is not set or is invalid.
The below is about my flow design
I’m, implementing a Dispatcher-Performer pattern using REFrame work. Both flows are implemented in separate ReFrame work .The Dispatcher is working perfectly and uploading data to the Orchestrator Queue. But, the Performer project is failing.
My Questions:
- Is this “Split-Workflow” approach inside the REFramework Process State the standard way to handle persistence?
- Are there better “out-of-the-box” templates for REFramework + Persistence that I should be using instead?
- Has anyone seen the
taskInputerror specifically when passing the Task Object between invoked workflows in Main?
Any guidance on the correct “Architecture” for this would be greatly appreciated!
Hi @aparna.dhanesh,
I did check but Orchestration Process template is not available now which was specifically designed for these type of use cases - might be deprecated. (check if it’s available for you)
- This approach is correct as you are automating transactional process, but for performer, Re-Framework is not ideal as your need persistence activities to be used.
- There was a template Orchestration Process which I also did use, but currently I am not able to see it although the official documentation says it is available.
- This error indicates that you have not provided the task (action centre task) is not provided which is required - how to resolve? You need to use Create Form Task activity or any other required activity where design the task form and it’ll give you task as output which can be passed to this activity.
Some addition information to guide you:
Orchestration Process documentation: Studio - Orchestration Process
Ideal Approach (based on orchestration process):
Limitations: 1. Cannot use foreground activities & UiAutomation (Workaround - create another simple process to perform this task and invoke inside this process)
Approach:
- Create Background Process Or Re-Framework with Persistence enabled.
- Divide process in 2 phases (in performer): Before action center & after action center
- Build init part in the process, can copy from RE-Framework
- Build Part 1(before action center): Get transaction item → business logic → Create form task - add this to a list of tasks - set tranaction status
- Build Part 2 (after action center): take Parallel For Each activity (normal for each won’t work) → Wait for Form task or other approproate pairing activity as per you create task activity → This will create wait for all the action center tasks to be completed, then only bot will resume → Write post processing business logic → once resumed this part will process all the items
- Note: Exception handling should be taken care so that bot will not get faulted. For the transactions where action center not required, logic should be written to process.
If this doesn’t suit your scenario, you can check out Document Understanding Process template which also work on persistence and follow different approach (processes each queue items seperately).
Happy Automation!
Thank you for the suggestions. It was very helpful for me to understand the concept.
Good to see it was helpful! Please mark as solution if helped so other also can refer the solution for similar problems.