UiPath Agentic Automation

What I like most about UiPath is its ability to simplify and accelerate automation development through an intuitive and well-structured environment. The platform offers a rich library of pre-built activities, connectors, and templates that significantly reduce development time and allow us to focus on solving business challenges rather than building everything from scratch. I also value its strong orchestration and monitoring capabilities. UiPath Orchestrator provides full visibility of our automation ecosystem, making it easy to schedule, manage, and scale robots as our needs grow. This has been essential for maintaining reliability and operational continuity to automated processes. Additionally, the constant evolution of the platform, especially with AI-powered features, document understanding, and improved integrations, has enabled us to expand use cases and deliver more impactful automation initiatives across the organization.

Studio was super easy to learn, a great marketplace to access pre-developed activities, and the ease of actual automation. Orchestrator is the perfect tool for scheduling, managing, and the tracking of processes. Lastly, Agent Builder makes it super easy to create agents. I did struggle at first as UiPath kept changing the model but now it seems like they have a base in place and are just adding new features.

What I like most about the product is how seamlessly it brings powerful agentic capabilities together with an intuitive learning experience. The rapid innovation, thoughtful features, and strong community support make it easy to adopt, experiment, and continuously grow while building real-world solutions.

Some of its components, especially those related to advanced automation, AI features and document understanding, still require considerable configuration effort and can feel complex for new or non-technical users. While the platform is useful, achieving optimal performance sometimes involves navigating multiple tools, packages, or dependencies that are not always straightforward.

There is no global view of the daily or weekly schedule. I think it has to do with Queue triggers but with the dispatcher/performer process layout, it should be able to create a step back view of scheduled automations. Analytics is great but there needs to be a way to select what queues/processes are calculated into savings. Lastly, there needs to be a way to mass update libraries across all processes. When a change happens, they have to be manually updated.

What I probably dislike is the analytics around AI unit usage, which could be updated faster and made more real-time to provide better visibility and control.