Resource estimates for converting an RDA to an RPA
We are looking at converting some RDA's to RPA's and have been asked to give some high-level estimates on this conversion. For example if the original RDA took 2 developers 2 weeks, could we estimate the conversion to take the same resource effort, or could we estimate half or some fraction? Assume the thought process into servers, configuration, error handling has been done. I am looking to see if anyone has done this and has some experience. thanks,
The conversion effort is really dependent on the use case and whether it is already tailored to what an RPA would do. For instance, a RPA process should include only the process to perform a single activity (doing multiple activities is handled by Robot Manager). An RDA process might include a loop structure to handle multiple activities and managing that part of the process. If the RDA process has logically separated the looping from the performing of the single activity it may be possible to convert to an RPA process rather quickly. If the logic is not separated it may require extensive recoding.
here is the Scenario - RDA Developer is given RDA project to 6 users to install in our laptop to do process automatically, after few days we identified bug, RDA developer fixed that bug and asked us to update new project in all 6 agents laptop. Did RDA works like that? Or is there anyway we can centralize in 1 place?
I am pretty naive in this area. This is what i am aware of.
You need to install robotic runtime at enduser's mechine and put the project in the a shared server. The runtime should run the project from there. So, anytime if there is a bug bug fix, you just need to update the project file in the server. Nothing needs yo be done at clients mechine.
But in case new project is created in different robotics version then you need to run robotic runtime of that version to each end users mechine.
That is correct. You can centralize the location of the RDA package by uploading the package to a shared server and changing the StartupProject setting inside of the RuntimeConfig.xml to point to the location of the uploaded package.
For large scale deployment, I would recommend considering using a more versatile approach such as Robot Manager, but for 6 users, the shared drive should be fine.