BTP & Integrationintermediate

BTP Build Process Automation Part 5: Desktop Automation and RPA

Key takeaway

Automate UI-based tasks with bots: the desktop agent, application capture (screens, elements), automation steps, attended vs unattended runs, error handling and when RPA is justified versus APIs.

Explanation

📌 KEY POINTS
✅ Automations run on machines with the desktop agent installed and registered.
✅ Application capture records screens and elements that bots interact with.
✅ Attended bots run with a user present; unattended bots run on scheduled/dedicated machines.
✅ Use RPA only when no API exists or for legacy UIs; APIs are more robust.
⚠️ UI changes (new versions, layout changes) break bots — plan maintenance and monitoring.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 4 covered APIs. Now UI automation.

━━━━━━━━━━━━━━━━━━━━
▶ 1. DESKTOP AGENT

Install, register, environment.

━━━━━━━━━━━━━━━━━━━━
▶ 2. CAPTURE

Screens, elements, criteria.

━━━━━━━━━━━━━━━━━━━━
▶ 3. AUTOMATION STEPS

Click, set, get, loops, Excel.

━━━━━━━━━━━━━━━━━━━━
▶ 4. RUN MODES

Attended vs unattended.

━━━━━━━━━━━━━━━━━━━━
▶ 5. ROBUSTNESS

Error handling, screenshots, retries.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Install and register the desktop agent.
Capture a web form and automate data entry.
Add error handling and test.

✅ CHECKPOINT: bot completes entries and reports failures.

Code example

ABAP Code

===== AUTOMATION =====Excel → read rows → for each row: open legacy web app → set fields → submit → capture result → write statusError handling: element not found → screenshot + log + continue with next row ===== DECISION =====API available? → use action | legacy UI only → RPA bot (attended/unattended)

Real project scenario

A company automated invoice entry into a legacy portal with a bot; a portal update broke the bot for a week unnoticed. Adding monitoring, stable selectors and a maintenance owner reduced disruptions.

Common mistakes

RPA when APIs exist.
Fragile selectors.
Personal credentials.
No monitoring.
No owner.

Best practices

APIs first.
Stable criteria.
Technical users.
Monitor runs.
Maintenance owner.

Interview angle

Questions: "When use RPA?", "Attended vs unattended?", "How do you make bots robust?"
Strong answer: agent, capture, steps, modes, robustness.

Practice this lesson

Quick check

1. When should RPA bots be used instead of API actions?

2. What is required on a machine for bots to run?

3. How can bots be made more robust against UI changes?

Interview questions

1. You inherit an existing SAP Build Process Automation implementation covering Build Process Automation Architecture: APIs, Task Center, Work Zone and Governance. What would you review before changing it, and what would make you confident the change is production-ready?

Answer it in your own words first, then compare.

2. A production issue is reported in SAP Build Process Automation around SAP Build Process Automation: Actions, APIs and Process Visibility. How would you troubleshoot it systematically and avoid the common failure patterns?