Also as suggested by Will Oprisko, take screenshot of the application you are trying to automate. Then open the screenshot to use the cv activities(e.g cv click, cv type Into etc)
Everyone is suggesting CV activities. Theyâre obsolete. You should be working in modern, and the modern activities have CV built in. You donât use the CV-specific activities. You just use the normal activities (ie click, type into, etc) and they have CV built in.
When using modern activities for a legacy application, when a descriptor cannot be identified, which is the case with legacy apps, does the CV kick in automatically and provide an identifier for the element? I do not see that happening.
The click or type into is identifying the whole block and not an individual element.
You donât need access to Orchestrator.
Just have to drag and drop the required CV activities and indicate elements with using those activities.
In property panel no need to add any API keys or anything thatâs related to Orchestrator.
You have to either turn on CV in the project settings for application selectors, or turn it on in the selector window as youâre indicating the target.