Lara,

The web adapter is currently the primary adapter that would be used for Automation Recording. The engineering team is working on expanding the use of this feature to other adapters in the near future. 

Automation Recording is most useful when you have identified a simple repetitive use case, with little to no discretion from the user's input. An example of that would be a login use case. The case requires three consistent input sequences, username, password, and then submission.

These variables will not change over the lifespan of the solution. Using the Automation Recording feature, minimizes the need for the developer to manually design an automation for such a repetitive task. When considering the use of this feature, be sure to ask yourself the following:

• How frequent will this use case appear in automation? (If often, the use case may be a candidate for Automation Recording feature)
• Is the input sequence dynamic or static? (Automation Recording works best with all static variables)
• Does this use case require decision-making from the user? (It is best to design the automation manually then use Automation Recording if the answer is yes)
• Are there any unknown variables that may appear? (If yes, please design the automation manually)

Thanks,

--Zach