Project 7 — Advanced

HR Onboarding Multi-App Bot

Ek naya employee join karta hai to 8 jagah kaam hota hai — folder creation, account request, welcome mail, tracker update, ID card. Ek ghanta manual. Is project me ek orchestrated bot banayenge jo sab kuch step-by-step kare — aur har step ka status track kare.

⏱ 30 min• Advanced• UiPath Studio (Community)

Project kya karega?

WHAT

Bot Excel/Action Center form se naye employee details lega — shared drive me uska folder structure banayega, welcome mail bhejega, HR tracker Excel me row add karega, IT ko account-creation request mail karega, aur ek onboarding status report generate karega. Har step ka status column — partial failure pe baaki steps chalte rahenge.

WHEN

Jab bhi employee onboarding 5+ steps involve kare. HR automation RPA ka fast-growing segment hai — "HR bot" searches badh rahe hain. Multi-app orchestration ka best learning project.

WHERE

HR tech companies, large enterprises (100+ hires/month), staffing agencies. Ye project dikhata hai ki tum single-app nahi, end-to-end workflow soch sakte ho — senior RPA developer ki pehchan.

Design principle: Multi-app bot me har app ek alag Sequence ho — invoke workflow file se call karo. Ek app fail ho to dusre chalte rahen, status column me "FAILED: folder" likha aaye. Ye "modular design" interview me impress karta hai.

Step-by-step build

Main.xaml (Sequence)
 |
 +-- Try Catch
 |    +-- Invoke Workflow File: 01_LoadData.xaml    (Excel/Form se employee data -> dtJoiners)
 |    +-- For Each  emp in dtJoiners
 |    |    +-- Try Catch  (per-employee isolation)
 |    |         +-- Invoke Workflow File: 02_CreateFolders.xaml
 |    |         |      root + emp("Name") + "\Docs", "\Reports", "\Assets"
 |    |         +-- Invoke Workflow File: 03_SendWelcomeMail.xaml
 |    |         |      To: emp("Email"), Body: template + Name + Manager + DOJ
 |    |         +-- Invoke Workflow File: 04_UpdateTracker.xaml
 |    |         |      Append Row: [emp details, DateTime.Now, "Onboarded"]
 |    |         +-- Invoke Workflow File: 05_ITRequest.xaml
 |    |         |      Send mail to it@: "Account creation: " + emp("Name") + " - " + emp("System")
 |    |         +-- Assign: emp("Status") = "Completed"
 |    +-- Catch
 |         +-- Take Screenshot  ->  "C:\Logs\error_" + DateTime.Now.ToString("yyyyMMdd_HHmmss") + ".png"
 |         +-- Log Message  LogLevel.Error
 |    +-- Invoke Workflow File: 06_StatusReport.xaml  (summary mail to HR head)

Modular XAML — 6 files, ek responsibility each

Project Structure:
00_Main.xaml          - Orchestration (upar wala flow)
01_LoadData.xaml      - Input: in_FilePath -> Output: dtJoiners (Arguments panel se pass)
02_CreateFolders.xaml - Input: in_EmpName, in_Root -> folder tree
03_SendWelcomeMail.xaml - Input: in_Email, in_Name, in_Manager, in_DOJ
04_UpdateTracker.xaml - Input: in_EmpRow -> tracker Excel append
05_ITRequest.xaml     - Input: in_EmpRow -> IT mail with system requirement
06_StatusReport.xaml  - Input: dtJoiners -> summary mail

# Arguments: in_ (input), out_ (output), io_ (both)
# Reusability: 03_SendWelcomeMail dusre bots me bhi use hoga

Error handling — partial success design

Per-step status: har step ke baad status update — "Folders: OK, Mail: FAILED". Debug 5 min me.
Continue-on-error: Welcome mail fail ho to tracker update skip na ho — Try Catch per invoke, status column me likho.
Manual approval (optional): Sensitive step (folder deletion, permission change) ho to Action Center task create karo — HR head approve karega, bot resume hoga.
Screenshot on error: Take Screenshot activity — visual evidence debugging me.

Enterprise tips

Input Action Center form se laao — HR khud web form bhare, bot turant trigger. (Orchestrator + Action Center integration.)
Folder template Config me — org structure badle to sirf config update.
Welcome mail me dynamic tokens (%NAME%, %MANAGER%) — template file Word/HTML me rakho, bot replace kare.
Onboarding tracker = single source of truth — audit me wahi dikhana hai.

Interview question: "Multi-app workflow me ek app fail ho jaye to?" — Per-app Try Catch + status column. Bot poora process na roke — baaki employees ka kaam chalta rahe, failed steps exception report me. Isko "graceful degradation" kehte hain. Senior level pe ye expected hai.

Exercise

Question: Error pe screenshot lene wali activity ka naam? (2 words)

Question: Human-in-the-loop approval ke liye UiPath ka kya service use hota hai? (2 words)

Common mistakes

Monolith workflow: Sab kuch ek XAML me = 500 lines, debug nightmare. Invoke Workflow File se modular rakho.
No status tracking: Bot fail hua, kis step pe pata nahi. Status column mandatory.
Happy path only: Mail server down, folder permission nahi — failure paths banao, tabhi production me chalega.
Rebuild logic: Folder tree har run pe delete-recreate = data loss risk. Exists check + create-if-missing.

Lesson complete?

Project ban gaya? Ab next project pe chalte hain — REFramework Production Bot.