Limitations of AA ver 11

What I found limiting in Automation Anywhere bot creation editing

1. [Begin Error Handling] Cannot throw custom error.
2. [Missing Command]
   1. No subtask or goto command. Needed in fail validation routine or repeated subroutine.
3. [Run Task] ̶N̶o̶ ̶e̶a̶s̶y̶ ̶w̶a̶y̶ ̶t̶o̶ ̶p̶a̶s̶s̶ ̶a̶r̶g̶ ̶t̶o̶ ̶b̶o̶t̶ ̶(̶.̶a̶t̶m̶x̶ ̶f̶i̶l̶e̶)̶.̶ ̶U̶s̶e̶ ̶$̶C̶l̶i̶p̶b̶o̶a̶r̶d̶$̶.̶ To pass arg or param to sub-task, in Run Task, select the radio button Variable to map Main Task Variable to Run Task Variable. However:
   1. it cannot set a value to a variable in sub-task.
   2. sub-task cannot stop parent task.
4. [$my-list-variable$]
   1. Impossible to access nth item in list dynamically.
   2. No easy way to assign list items to separate variables.
   3. Cannot assign one list to another without string operation.
   4. No way to get the length of list without looping.
5. [Loop] Cannot loop through windows.
6. [Add Variable]
   1. Cannot accept $ in regex expression.
   2. Cannot set value to another variable, eg, $AAApplicationPath$\temp.csv
7. [Edit Variable] No easy way to rename variable and have the new name updated in Actions List.
8. [Edit Actions List] No find and replace editing action.
9. [Debug Mode] Sub-task does not support breakpoint making it very hard to debug.
10. [Undo] does not undo var's value which was replaced.
11. [Workbench] When the connection to CR is lost, the workbench closes without warning. I lost all my works!
12. [Object Cloning]
    1. is slower than manual operation, eg, click or get text operation.
    2. No option to add mouse click or keyboard enter after setting text or value to an HTML input. Necessary to fire an event in the DOM.
13. [File] Cannot use Windows Environment Variables for file path, eg, %HOMEDRIVE%%HOMEPATH% for 'C:\Users\kiat'

The RPA Hype Cycle Is Over -- Here's The Reality Show archive.org snapshot

Pureplay RPA vendors are overselling their solutions and not speaking the truth about the reality of what an RPA bot can do.
Rolling out and maintaining an army of bots is a formidable challenge, and too often, the industry doesn’t acknowledge the realities of this challenge. This includes many RPA vendors and global systems integrators.
First, getting RPA solutions up and running demands a significant amount of coding work — both upfront and on an ongoing basis — that requires budgeting for professional services. Second, RPA bots are often brittle because they’re hard-coded to key fields. Therefore, small user interface adjustments can cause them to fail.
These glossed-over challenges could help explain why companies deploy and maintain far fewer bots in practice than they initially purchase.