You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TagUI RPA has been maintained by AI Singapore for several years. From Q4 2023, they will stop supporting it.
The natural evolution for TagUI users, to make the most use of developed assets like TagUI workflows, would be to assess if converting to Python rpa package scripts make sense. Since each TagUI step has a matching Python rpa function(), conversion should be pretty straightforward for any user willing to learn Python.
For the JavaScript sections in TagUI workflow files, there are online convertors to convert JavaScript code to Python code. There are also other considerations like how to deal with scripts written in human languages other than English, how to deal with object repositories, how to deal with data tables etc etc etc.
Creating a placeholder issue here so TagUI users can post their challenges and share solutions on migrating from the most popular open-source RPA tool (TagUI) to the most popular open-source Python rpa tool (this package 😄)
The text was updated successfully, but these errors were encountered:
kensoh
changed the title
Placeholder issue for TagUI users converting .tag workflows to Python rpa .py scripts
Market qquare for TagUI users converting .tag workflows to Python rpa .py scripts
Jul 9, 2023
kensoh
changed the title
Market qquare for TagUI users converting .tag workflows to Python rpa .py scripts
Market square for TagUI users converting .tag workflows to Python rpa .py scripts
Jul 9, 2023
kensoh
changed the title
Market square for TagUI users converting .tag workflows to Python rpa .py scripts
Meeting point for TagUI users converting .tag workflows to Python rpa .py scripts
Jul 15, 2023
TagUI RPA has been maintained by AI Singapore for several years. From Q4 2023, they will stop supporting it.
The natural evolution for TagUI users, to make the most use of developed assets like TagUI workflows, would be to assess if converting to Python rpa package scripts make sense. Since each TagUI step has a matching Python rpa function(), conversion should be pretty straightforward for any user willing to learn Python.
For the JavaScript sections in TagUI workflow files, there are online convertors to convert JavaScript code to Python code. There are also other considerations like how to deal with scripts written in human languages other than English, how to deal with object repositories, how to deal with data tables etc etc etc.
Creating a placeholder issue here so TagUI users can post their challenges and share solutions on migrating from the most popular open-source RPA tool (TagUI) to the most popular open-source Python rpa tool (this package 😄)
The text was updated successfully, but these errors were encountered: