Summary: This automation was built to download data from LEED to be pulled into the EDW. The automation will pull the entire set of data from LEED, and save the file as a CSV. This file will then be uploaded into an Azure storage container for the Data team to consume.
How to Execute Bot: The automation is scheduled monthly, so no action is required to trigger the automation.
Process Owners: Tom Goble
Bot Owner(s): Dan Hogfelt
Developers: Dan Hogfelt
Relevant Systems:
- Azure
- Excel
Business Continuity Plan: If Process fails, email to be sent to distribution list informing them that the process failed. A ticket should be created in DevOps for the bot issue to be investigated, fixed, tested, and redeployed according to change management practices. In this event, team should manually upload the files to Avant.
Expected Volume: This bot is executed once per month.
Credential Management:
LEED Credentials
Storage Buckets:
LEED
SLA: Provide up to an hour for each file to process
Scheduling: 1st of the Month
Triggers: LEED Upload
Queues:N/A
Assets:(Shared Folder)
- SMTP From Email
- SMTP Port
- SMTP Host
- SMTP Password
Reporting:
Distribution List: -List of people that the emails should be sent to from UiPath.
thomas.goble@avisonyoung.com, rpa@avisonyoung.com, dataarchitectureteam@avisonyoung.com
KPI's:
Runbook:
The runbook should provide information to support the bot in the case that any issue occurs.
If Bot Fails: An email will be sent saying the bot failed and what period failed to run. There are also messages being logged to the Orchestrator Tenant at the start and end of each major sequence to make it easy to see where the bot is failing.
DevOps Epic: https://dev.azure.com/AY-InnovationCenter/UiPath%20Automations/_workitems/edit/8203Automation Hub Link:
Comments
0 comments
Please sign in to leave a comment.