Looks like I need to brush up on my SAP automation knowledge. I'd be tempted to just say 'the answer is whatever makes the IBM RPA Recorder team the most money' and move on to the next question. But I suppose that's not the kind of humor they're looking for on this exam.
This question is really testing our knowledge of the nuances between SAP and Windows automation. I bet the developers who wrote this question have some hilarious stories about the 'fun' they've had trying to get the RPA Recorder to work across different platforms.
Hmm, I'm not sure about option B. Holding down different keys to identify the selector control doesn't seem intuitive to me. Maybe the RPA Recorder has a way to automatically detect the right key combination based on the target application?
Option C is the one that stands out to me. Having to click to identify the control selector in SAP is an extra step that doesn't seem necessary for Windows apps. I wonder if that's to account for some of the unique UI elements in SAP?
The differences between using the IBM RPA Recorder on SAP versus Windows applications are quite subtle, but I can see how they could trip up some developers. I'm leaning towards option D, since the vision driver requirement for SAP seems like a key distinction.
That's true. Also, SAP automation requires activating the vision driver in Recorder, whereas control can be directly identified for a Windows application.
Stefania
Delsie
2 days agoBrendan
8 days agoSerina
12 days agoLinette
16 days agoPearlene
24 hours agoTamar
21 days agoTammi
22 days agoTamar
23 days ago