Install
Download the Bot and follow the instructions to install it in your AAE Control Room.
ConfigReaderUtility(CSV)
Reads CSV configuration into a dictionary and creates standard project folders, simplifying setup and centralized management of unattended automations.
Top Benefits
- Centralized Configuration – Manage all settings in one CSV file.
- Faster Setup – Automatically creates the standard folder structure.
- Easy Maintenance – Update paths, URLs, or settings without changing bot logic.
- Consistency – Ensures the same folder structure across automations.
- Reusability – Use the same configuration bot across multiple unattended bots.
Tasks
- Read and validate configuration from CSV
- Load configuration values into a dictionary
- Create standard project folder structure
- Configure paths, URLs, process names, and settings
- Capture and track errors with task details and line numbers
Setting up a new unattended automation usually means hard-coding paths, URLs, and folder names directly into the bot — and repeating that setup, folder by folder, every time. The Read Configuration Bot (CSV) removes that repetition. It reads a simple two-column CSV file (Key, Value) and loads every setting into a single dictionary variable, ready to use anywhere in your automation. At the same time, it builds the standard project folder structure — Input, Output, Screenshots, Logs, Temp, Archive, AuditLog, ErrorLog — under the root folder path you specify in the config, using the process name you give it.
Inputs and triggers: A Control Room (or local) CSV file containing Key/Value configuration rows — environment name, root folder path, process name, sub-folder names, application URLs, retry counts, and so on.
Actions: Reads the CSV, stores every value in a dictionary variable, and creates the folder structure under the given root folder.
Outputs: A dictionary variable (dConfig) holding all config values, plus error-tracking variables (task name, today's date, error flag, error message, line number).
Use cases: Any unattended bot that needs centralised settings and a consistent folder layout — so a change to a URL, path, or credential is made once, in the config file, instead of hunting through bot logic across multiple automations.