In this month's Developer Meetup,
Key Highlights
Web Triggers & Connector Builder
Web Triggers are the "caffeine boost" for automations, enabling instant responses to enterprise events. Unlike traditional event triggers, Web Triggers:
-
Listen to cloud events without requiring bot runner infrastructure
-
Support multiple platforms including GitHub, Jira, Office 365, and ServiceNow
-
Provide real-time automation triggering capabilities
Vineet showcased a live demo (starts at 16:38), building an email assistant using:
-
Connector Builder to create an NVIDIA AI integration in minutes
-
Web Triggers to monitor Outlook mailboxes
-
API Tasks to process incoming emails and attachments
-
Enhanced Observability Features
Deven unveiled new monitoring capabilities coming in A360 v.36 (starts at 51:51):
New Monitoring Dashboard
-
Real-time visibility into automation status
-
Smart filters for different automation states
-
Export capabilities for reporting
-
Future enhancements will include trend analysis and AI-assisted troubleshooting
License Analytics
-
Detailed usage metrics for different license types
-
Identification of underutilized licenses
-
Bot creator activity tracking
-
Trend analysis for license consumption
Resources & Next Steps
-
Try it out: Web Triggers are available now in bots and coming to API Tasks in v.36
-
Learn more: Delta Training for the Automation 360 .35 Release is available on Automation Anywhere University
-
Stay connected: Check out our event calendar for upcoming Developer Meetups, Product Clubs and more.
Thanks to all our Pathfinder Community members who attended and shared feedback on improving dashboard improvements and metrics tracking capabilities.
Q&A
Q: How is the Postman collection generated? How do we get it?
A: Here's a link to the Postman collection used today: https://vineetonpostman.postman.co/workspace/1926e0ec-e8a0-4c5c-8d7c-b6e7a7aaa2b3/folder/19710860-090fe761-6dfb-48a0-9b2f-56efc8b15aa0.
Q: How to promote the connector from one environment to another environment? Like dev to UAT to PROD.
A: When you promote your automations to different environments, export the bot including the packages, so that the package gets moved over. You can also export the connector outside of the bot as well. There is a download option in the "Published" tab to download your connector. You can then upload this connector to any other CR.
Q: Do we need VMs to run such task bots?
A: Yes, you will need a bot runner to run task bots; however, API tasks do not need bot runner machines.
Q: How can I find more information about the OAuth credential in the web trigger? I have never used OAuth before.
A: "These documentation pages may be worth checking out:
https://docs.automationanywhere.com/bundle/enterprise-v2019/page/create-oauth-connections.html
https://docs.automationanywhere.com/bundle/enterprise-v2019/page/web-triggers.html
https://docs.automationanywhere.com/bundle/enterprise-v2019/page/create-wt-ms365-outlook.html"
Q: What information about email is getting passed from the Outlook email trigger to the bot, like how the code identifies which email to process?
A: There is a unique mapping between the mailbox and the subscription generated in the Event triggers page. That's how the bot knows that the email has arrived in the configured mailbox. A lot of information is available in the event payload, some of which are Outlook message ID, has attachment, etc. The full list is available on the docs portal.
Q: How do web triggers work in real-time on the below scenario: Let's say at once 10 emails are received. Now 10 times the BOT triggers, or does it trigger only once and process all 10 emails?
A: The automation is triggered 10 times.
