It's common to have doubts about entering a conversion project. If you have production bots that you can share with us that the current conversion is not getting right, please get in touch with us via our Developer Slack or Forum You do not need to share the entire robots with us anymore as running our tooling locally generates schema.csv, which does not contain any business logic or data but enables us to improve the conversion logic. We are improving the conversions for each source system based on feedback and the available source material. VS Code extension also gets the updates to the conversion and analysis tooling almost instantly, so that is the way to get the latest and greatest version we have available. Still, we recommend using VS Code as the use cases for conversion are often on the complex side, and VS Code provides you with the widest toolset possible. The tooling is available in our VS Code extensions and Automation Studio. We also have a very initial version of Automation Anywhere v11 conversion tooling out, but we need more example robots to improve that logic, so if you have any, please get in touch with us. On the conversion side, we have beta-level logic for BluePrism, Automation Anywhere 360, and UiPath available. The development status as of February 2023 is that we have the analysis support for BluePrism, UiPath, A360, and AA v11 that enables you to gauge the complexity of your robots and find the parts of the robots that you can and should see as a common component. We are developing conversion and analysis tooling for BluePrism, Automation Anywhere and UiPath. Most of the items raised are things we recommend having in place for all automation projects, even if you are not considering conversion. The main focus is on the process and helping you make the decision and have the confidence of where to start. This section holds the best practices and guides for converting existing Gen1 bots to Robocorp.
0 kommentar(er)
