How adityasagave/shipment-booking-automation works
Project type and purpose
• This is a no-code/low-code automation solution built with Microsoft Power Automate Desktop.
• Purpose: Automate shipment booking tasks (Excel form prep, Word doc edits for CI/CSD, Outlook email sends and inbox monitoring, print dispatch) to save time and reduce errors.
File structure
• Top-level files:
• LICENSE (project license)
• Power-Automate-language.wdl (workflow definition in WDL format)
• README.md (documentation)
• No separate code directories—this is a single PAD (Power Automate Desktop) flow defined in the WDL file.
• Supporting assets are in predefined folders specified in the README (Booking form-offline, CSD-offline, CI-offline, signature images).
README for architecture insights
• Core workflow stages:
a. Input collection (date, weight, dimensions, agent selection).
b. Excel automation (populate booking form).
c. Word automation (populate CI & CSD docs).
d. Outlook integration (send initial emails, monitor inbox, parse Job ID/AWB via regex, send final emails).
e. Print automation (auto-print final CI & CSD).
• Technical stack: Power Automate Desktop, Excel, Word, Outlook, Regex, file/date/loop controls.
a. Main components:
• User Interface (PAD UI dialogs)
• PAD Flow Engine (core workflow)
• Excel Service (reads/writes .xlsx)
• Word Service (reads/writes .docx)
• Outlook Service (SMTP send, inbox monitor)
• Regex Parser (Job ID & AWB extraction)
• File System (template storage, signature images, output folder)
• Printer Service (auto-print documents)
b. Relationships & interactions:
• User launches PAD flow → UI dialogs collect inputs → PAD Flow Engine
• PAD Flow Engine calls Excel Service → reads template, writes data → saves booking form
• PAD Flow Engine calls Word Service twice (CI, CSD) → populates fields, images, tamper tape numbers
• PAD Flow Engine calls Outlook Service to send initial emails → monitors inbox
• Inbox messages → Regex Parser extracts Job ID & AWB → PAD Flow Engine updates Word docs → Outlook Service sends final emails
• PAD Flow Engine calls Printer Service → sends CI & CSD to printer
• PAD Flow Engine writes output files back to File System
c. Architectural patterns/design principles:
• Orchestration pattern: PAD Flow Engine orchestrates multiple application connectors.
• Modular adapters: Excel adapter, Word adapter, Outlook adapter, Regex processor, Printer adapter.
• Single workflow file (Power-Automate-language.wdl) defines logic, loops, conditions.
d. Key technologies:
• Microsoft Power Automate Desktop (workflow engine)
• Microsoft Excel & Word COM automation
• Outlook Desktop COM automation
• Regular expressions for parsing
• Local file system for templates & outputs