- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Automation enthusiasts, rejoice! If you're an RPA release manager or administrator, you'll love this game-changing feature in RPA Hub—Skill Version Overrides. Whether you're streamlining processes, ensuring consistent bot behavior, or juggling multiple versions of a skill, this feature is your ticket to unparalleled flexibility and control. Let’s dive into the why, what, and how of overriding skill versions.
Why Skill Version Overrides Matter
Imagine this: You’re managing multiple bot processes, each requiring different functionalities of the same skill. Previously, any version change meant republishing your automation package—a time-consuming and disruptive task. Not anymore! With Skill Version Overrides, you can:
- Use specific skill versions for different bot processes without republishing.
- Ensure stable, predictable automation workflows tailored to each process.
- Save time and effort while maintaining flexibility and control over automation.
Say goodbye to unnecessary changes and hello to seamless customization.
What Exactly Is Skill Version Override?
Skill Version Override lets you assign a specific version of a skill to individual or multiple bot processes in RPA Hub. When your bot process executes, it uses the overridden version, not the default version defined during development.
A Real-Life Example
You’re managing two bot processes:
- Shipping Management: Requires version 10001 of the Excel Operations skill.
- Data Reconciliation: Needs version 10002 of the same skill.
Instead of republishing these processes, you can simply override the skill version for each process. This way, both bots can execute with their respective skill versions seamlessly.
Key Benefits
- Effortless Customization: Use different skill versions without republishing packages from RPA Desktop Design Studio.
- Enhanced Stability: Assign the exact version needed for a bot process to ensure predictable results.
- Streamlined Management: Easily update or switch skill versions in RPA Hub with minimal disruption.
- Multiple Process Support: Override skill versions for several bot processes simultaneously, saving time and reducing errors.
How to Use Skill Version Overrides in RPA Hub
Ready to take advantage of this feature? Here’s a step-by-step guide:
Override a Skill Version for a Bot Process
- Navigate to All > Robotic Process Automation > RPA Hub Workspace.
- Select the list icon .
- On the Lists tab, under Build, select Bot Process.
- Open a bot process that you want to override a skill package version for.
- On the Skill Overrides tab, select the skill version that you want to override.
- In the Overridden version field, select the version to override.
That’s it! The selected skill version is now assigned to your bot process.
Override Skill Versions for Multiple Bot Processes
- Access Packages: In the RPA Hub Workspace, select Packages under the Lists tab.
- Choose the Skill Package: Open the relevant package and go to the Package Versions tab.
- Select Bot Processes: In the Bot Process tab, click Edit and select the bot processes to apply the override.
- Save Changes: Confirm your selection, and the overridden version will apply across the selected processes.
Things to Keep in Mind
- Ensure the bot process is not in the Published stage before making overrides.
- If upgrading to Xanadu, republish your attended or unattended packages to view associated bot processes.
- The feature requires specific roles: sn_rpa_fdn.rpa_release_manager or sn_rpa_fdn.rpa_admin.
Why This Matters to You
This feature empowers you to maintain control over your automation ecosystem like never before. Whether you're dealing with frequent updates, diverse requirements, or tight deadlines, Skill Version Overrides let you fine-tune each bot process to perfection.
So, what are you waiting for? Start exploring the power of Skill Version Overrides today and revolutionize how you manage automation processes in RPA Hub. Your bots will thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.