To illustrate the same visual identity as our company, we've updated Cloud Platform with the new colors and logo.
Having heard your feedback on the two-step user management process within Cloud Platform, we've thought out a new, easier method. Before, you had to invite users into the account, and then add them to each of the services they needed to access.
The reengineered Invite User page now allows you to invite the users, grant them roles within your account, assign them to services and grant them specific service level roles.
Of course, you can still invite people to your account first and decide later on their assigned services and roles.
We’ve enabled SmartCard authentication support for the Unattended Robots in your Cloud Platform services.
- There were inconsistencies in the number of Studio licenses assigned by default to a service in Cloud Platform accounts on the Community plan and the number displayed when accessing that service.
- The changes performed on the Profile > Alerts page of your Cloud Platform's Orchestrator tenant were not saved because users didn't have the Edit permission on Users. We enabled this permission for Cloud Platform users so that now you can configure alert settings as you wish.
- Neither the Audit Log nor the
CSVlog file downloaded from your Cloud Platform contained references to any operations regarding StudioX or Computer Vision licenses. We've corrected both errors.
- Demo packages and processes are no longer provided within your Orchestrator tenants for newly created Cloud Platform accounts. We've removed them because they might be incompatible with your installed Studio version and throw errors at runtime.
- If you tried to access a Cloud Platform account to which you were not invited, you received an ambiguous error message and you got stuck on that page. The message displayed now is "<email address> is not part of the account you're trying to access. Continue by logging in with a different user. "
- The information in the Automation Quick Start section on the Services page wasn't displayed in Japanese even if you chose to localize your account in this language.
Due to an Elasticsearch limitation, Cloud Platform's Orchestrator tenants are configured to ignore Robot logs larger than 50 kb. The vast majority of logs average around 2 kb so this setting shouldn't impact most of you.
Our next LTS release is soon approaching and as a not-so-sneaky sneak peak, we bring to you a myriad of features and improvements - all aimed at improving your UiPath experience, regardless of the deployment scale you're at. Our hard-working research and development team brings you enhancements in terms of resource organization at scale, collaboration inside your Center of Excellence, queue management, and why not, leave a little room for a human in your loop. For more than this TLDR version, please keep on reading.
Aimed at keeping your RPA deployment manageable and organized no matter the scale, the latest UiPath Orchestrator release introduces the Folders feature. There are now two organizational paradigms available in Orchestrator: Classic Folders and Modern Folders. Through classic folders, full backwards compatibility is maintained for your existing deployment and integrations while enabling you to segregate at the tenant level those divisions of your business that are wholly separate. Moving beyond the classic model, modern folders enable you to easily manage resources, and access to them, through support for hierarchical structuring of your Orchestrator instance combined with the new ability of fine-grained role assignment - your Orchestrator instance can now be structured inline with your corporate structure with each level, or employee, only having access to those resources needed for their role.
The previous experimental Organization Units feature is now fully supported as part of Orchestrator's Folders functionality. You can organize your instance using any number of classic and/or modern folders. Like OU's, classic folders are separate, flat structures with no shared Orchestrator entities between them. Modern folders enable you to create hierarchical structures, with users inheriting access to any subfolders of a folder to which they are assigned. User access in modern folders can be managed with greater granularity by creating custom roles and setting the desired permissions on a per folder, per user basis. Learn more about folders here.
Attended Robots Auto-Provisioning
Remember Floating Robots? In the context of modern folders, they come with no strings attached, and possibly the smallest deployment effort so far. Their execution capabilities can be put to use across modern folders, unrestricted by any form of organization. This brings great value especially alongside hierarchical folders, as you may structure your data as you desire, and make the execution force fit it perfectly as is. Don't blink too fast. These Robots can be automatically created for whatever type of user identities you have in your instance, and license-wise, they are configured on the spot on a per-user basis. Might seem a lot, but this can actually be achieved with roughly 5 clicks.
For a better collaboration between RPA developers and Orchestrator managers, you can now view the graphical representation of any package version uploaded to Orchestrator, just as you do in Studio's Designer panel. You can see which
.xaml file is marked as Main for a project, deep dive into any workflow, view a project's dependencies, and look up any activity property and its value. For a better picture of the entire feature, click here.
This release graduates key features in handling long-running workflows, introducing support for processes that require logical fragmentation or human intervention. Among other things, this paves the way for intuitive and easy invoice processing, exception handling and performance reviews. We set the stage for automating complex processes that either rely on the completion of other processes, or require approval or validation, all this with minimum downtime and no waste in terms of resources while waiting for process resumption. Learn more about it here.
Don't worry, we've introduced a new project template in Studio, and a brand new set of activities that allow the smooth fragmentation of your workflows. In this scenario, Orchestrator introduces the human in the loop and ensures a smooth management of your fragmented jobs.
The human aspect is handled through tasks which can be managed and completed without obstructing process unfolding. After human intervention is made and task completion takes place, resources are allocated for job resumption, thus ensuring no waste in terms of consumption. Details here.
Scheduling in Orchestrator has been treated to a major overhaul to make everything easier and more intuitive to use. The functionality is now called Triggers and comes along with a couple of new features and improvements. The highlight is that you no longer need to make arrangements to optimize the processing of your queue items. Orchestrator gives you the possibility to trigger a process whenever new queue items are available in your queues. Be reminded, since scheduling is not possible for attended use cases, and modern folders only work for those, this goodie is available for classic folders only. For now. Details here.
This is not all. We implemented a Queue SLA tool which gives you better control over the processing time of your queue items, and helps you assess what resources you need to allocate such that the items are processed in time. Whenever the SLA is in danger of not being met, you are properly notified such that you can make adjustments accordingly.
Individual transaction items from your Queues can now be edited or cloned, enabling you to change the priority or deadline to suit business needs. This feature also enables you to download a
JSON file of the transaction data to review and upload it if any changes were needed. More details here.
You now have greater control of the data flowing through your queue items, making further processing and analytics that much easier. When creating a new queue, or editing an existing one, you can upload custom
JSON schemas for the Specific Data, Output Data, and Analytics Data generated by all future transactions to be validated against, ensuring any successfully processed queue item has a reliable form of data.
Some good news is afoot - if Studio is licensed locally, no additional license is consumed in Orchestrator. Furthermore, each time you create a Robot, you can specify if it uses an external license or not. While we were here we also renamed this type of license to Studio, to avoid confusion.
Creating and managing Assets is now simpler, no more creating single value or robot specific value assets. When creating an asset you now have the ability to add a global value. This global value serves as the default provided to any robot which does not have a specific value assigned to it. Read more about it here.
The first ever version of the Non-Working Days feature allowed you to define one set of non-business days in which your schedules were not triggered. We made it better. You can now create multiple calendars per tenant, each with its own set of dates, such that whatever restrictions you want to impose, they can be granularly controlled. To get one more thing off your chest, we also added the possibility to upload a CSV file containing the dates to Orchestrator, no extra manual intervention required. Find out more.
To ensure all of your processes are using the latest package version, you can now see all eligible processes when uploading a new package and upgrade any or all of them instantly. See here more details.
The newly added Restart Job feature saves you valuable time by enabling you to quickly run a job from the jobs list. You’ll be glad to know that you can restart any job with a final state – Stopped, Faulted or Successful. The decision to modify the previous settings of the job lies in your hands. Please keep in mind that you can change the job’s input parameters and robots, and that you can’t restart jobs triggered by an agent.
Almost forgot about this one. To fit this finely-crafted work of code, testing and brainstorming our company went through while working on this release, we made some changes to our interface such that everything is organized better in the menus. We wanted to give it a more intuitive design, such that you find it easier to use and have a smooth user experience. You probably won't at the beginning, but give it a try. Trust us on this one.
Lastly, as a continuation of our efforts to reach out to the entire world and make automation a language everyone can speak, the entire platform is now available also in Spanish, Spanish Latin America, Portuguese, and Turkish.
In our continuous quest to improve your automation experience, we enriched the Services page with a quick start section that contains valuable information and download links for Cloud Platform's components: Studio, Orchestrator and Robot. View our Intro video clicking a single button, collapse and hide the entire section on demand, or restore it to display its information at your desire. Read about it here. Note that the information in this section is displayed in English even if you choose to localize your account to Japanese.
Starting with this release, users added to a service within Cloud Platform are automatically added to the Default Classic folder of that service, if it exists and it hasn't been renamed.
The information about your licenses is presented intuitively now in the Licenses page, being split up in three categories: Robots, Studios, and Other Services, each in their separate tabs. The same three categories assist in your decision when you are renewing your licenses or requesting more licenses.
Your Resource Center page just got richer with a download link to the newest Preview version of Studio, besides the already existent Stable version. It's for you to decide whether you wish to try out our latest innovations in your workflows or go with the less updated and more stable version of Studio.
We are no longer able to support Cloud Platform in Ukraine. We are deeply sorry for the inconvenience.
Operationinformation was not displayed in the Audit Logs page for logs that involved the generation of new API keys for the services available within Licenses > Other Services tab.
- We fixed a known issue that caused the service sessions running in duplicated browser tabs to expire, despite being actively used, when one of the sessions associated with the service expired. This used to happen because multiple Orchestrator tabs were not in sync.
- Some links on the Resource Center page used to point to the English version of the page despite you choosing to localize your account to Japanese. Note that a few links are available only in English for the moment.
Updated 26 days ago