- SAP Managed Tags:
*** Update ***
The recorded presentation of the What's New 2004 for SAP Intelligent RPA is available here.
Hello everybody,
The SAP Intelligent RPA team is pleased to share with you the new features and improvements of the 20.04 release. Please note that some enhancements were introduced with the 20.03 release.
General
On-Premise Components: Improvements to Connectors
Improvements to Cloud Components
Starting with the 2003 version, some of the quotas in the trial version of SAP Intelligent RPA have been increased:
For more information on the available quotas in the trial version, see the corresponding page in the SAP Help Portal.
With the 2004 release, new activities and methods for PDF have been introduced in the Desktop Studio. With these activities and methods, you can now open and extract text from readable PDF files.
Convenient activities that you can drag and drop in the Desktop Studio allow you to:
More powerful SDK functions are also available to give you even more control over the extraction of text from readable PDF files.
Further connector improvements are available with the SAP Intelligent RPA 2004 release, including enhancements to SAP GUI for Windows.
A new “Click Button Cell” activity is now available for the GuiGridView component, making it possible to click a button that’s in a table cell.
In addition, new scrolling features have been added for the GuiUserArea component:
With the 2004 release, we have added a multi-template matching feature. Template matching supports the detection of any pre-selected pattern on a user interface, including non-textual areas, regardless of the target location. The multi-template matching feature increases matching accuracy when there are multiple candidates for an image pattern on the screen.
Multi-template matching provides a way of identifying the location of the target image pattern at runtime which doesn't depend on precise coordinates: using a reference label specified through the "Labelled By" property.
In the example screen below, we want to target the checkbox template that’s labelled by "Checkbox7". At runtime, the correct checkbox is identified by means of this label, even though there are multiple hits.
Using item coordinates at design time to identify text items on an application page doesn't always deliver the required results. That's because page layouts at runtime can vary. With the 2004 release, you can now choose to use the nearest matching text along the x or y axis or a combination of both. You can configure this on one or both of the following item properties:
For both properties, the value can range between 0 and 100. The default value is 0, meaning that this feature is disabled. If the deviation at runtime is greater than the configured percentage value, the text is not recognized.
If the name of a package is changed during the acquisition, this is now shown in the Factory‘s Acquisitions view.
12 new additional bots are now available in the Store with the 2004 release of SAP Intelligent RPA.
The user interface of the Cloud Studio has been redesigned to make it more intuitive.
The User Tasks interface was improved in the 2003 release. Creation of user tasks has been simplified: There are no longer optional headers or footers, and a new title component is now available.
The top-level tabs in the Cloud Factory have been changed in the 2004 release: The Deployments and Management tabs have been replaced by new Agents and Environments tabs.
On the Environments tab you manage the packages, triggers, variables and agents used in your environment. You also manage access rights to your environment.
On the Agents tab, you monitor your agents in the Agents section and organize them by machines or users in the Agent Groups section.
With the new Agent groups concept, you organize the agents available in your organization. It replaces the former hierarchy variables. You can group your agents according to two criteria: groups of machines and groups of logins.
Adding an agent or an agent group to an environment links agents to an environment so that packages/jobs can be distributed to them. To select the agents used in an environment, you now use the Environments tab.
The new Environments tab is the entry point to the Cloud Factory: This is where you define and edit the functional landscapes in which your automation (scenario or process) is deployed and executed.
Environments form a shell grouping all of your project's resources in one place: triggers, packages, variables, and agents.
With the 2004 release, the deployment of packages now takes place behind the scenes. A trigger wizard is directly launched from the Packages tab: An “Add Triggers” button replaces the previous Deploy button.
The new trigger wizard also provides an option to minimize the number of package versions per environment.
With the 2004 release, the package versioning has been improved to solve existing limitations. Inspired by the classic software release mechanism, the versioning scheme of the packages is now:
[Major_Version].[Minor_Version].[Build_Version]
The Major version indicates important modifications potentially leading to incompatibility between versions. The Minor version indicates smaller modifications and bug fixes. The Build version indicates technical information and how many times a package has been generated.
The package is displayed in the Factory as follows: Version 1.0 (Build 1). Only the build version value increases with each update. For example, the second build of Version 1.0 (Build 1) is Version 1.0 (Build 2).
Each released package version has a unique major.minor pair.
Lifecycle management of packages has also been improved with the 2004 release. Changing a package version is the recommended approach to upgrading your deployed packages. With this approach, changing a package’s version doesn't remove previously assigned triggers.
In an environment, packages and triggers are distinguished by colors indicating their status: blue (enabled), gray (disabled) and orange (for triggers, when the associated package is disabled or in error).
The UI of the environments also displays any errors, including deployment errors.
You can now share an environment and its rights with other users. All the resources of an environment (agents, variables, packages and triggers) also inherit the rights of this environment.
With the IRPAProjectMember role you can now create environments. If you’ve been granted read access, you can also see the list of agents within an environment.
That’s all for the 2004 release. As usual, some technical improvements have also been introduced. Don’t forget to browse our community and our help portal for further information. Stay tuned - and happy bot-building!
Best,
Guillaume on behalf of SAP Intelligent Robotic Process Automation Team
For more information on SAP Intelligent RPA:
The recorded presentation of the What's New 2004 for SAP Intelligent RPA is available here.
Hello everybody,
The SAP Intelligent RPA team is pleased to share with you the new features and improvements of the 20.04 release. Please note that some enhancements were introduced with the 20.03 release.
General
- Trial (2003)
On-Premise Components: Improvements to Connectors
- Document processing - PDF
- Enhancements to SAP GUI for Windows
- Improvements in surface automation
Improvements to Cloud Components
- Store
- Improvements when getting a package from the Store
- Additional bots
- Improvements to Cloud Studio
- New UI layout
- User task improvements (2003)
- Cloud Factory - new behavior
- New tabs: Agents and Environments
- Agent groups
- Environments
- Trigger wizard
- New package versioning and lifecycle management
- Visual assistance and error management for environments
- Improvements for authorization and sharing
General
Trial (2003)
Starting with the 2003 version, some of the quotas in the trial version of SAP Intelligent RPA have been increased:
- Up to 20 clouds projects can now be created, instead of 10 previously.
- Up to 30 packages can be generated or imported, instead of 20.
- Up to 30 triggers can be created instead of 20.
For more information on the available quotas in the trial version, see the corresponding page in the SAP Help Portal.
On-premise Components: Improvements to Connectors
Document processing – PDF
With the 2004 release, new activities and methods for PDF have been introduced in the Desktop Studio. With these activities and methods, you can now open and extract text from readable PDF files.
Convenient activities that you can drag and drop in the Desktop Studio allow you to:
- Get the full text
- Use filters to retrieve or search specific pages or areas on a page
- Match unique patterns (such as invoice numbers, prices, or dates) with “Extract text with regex”
- Search for specific words and get the exact position of the results
More powerful SDK functions are also available to give you even more control over the extraction of text from readable PDF files.
Enhancements to SAP GUI for Windows
Further connector improvements are available with the SAP Intelligent RPA 2004 release, including enhancements to SAP GUI for Windows.
A new “Click Button Cell” activity is now available for the GuiGridView component, making it possible to click a button that’s in a table cell.
In addition, new scrolling features have been added for the GuiUserArea component:
- “Scroll to next page” activity: If there is a vertical scroll bar, scrolls down to bring into view content that’s below the screen level.
- “Scroll To previous page” activity: If there is a vertical scroll bar, scrolls up to bring into view content that’s below the screen level.
Improvements in Surface Automation (OCR)
Multi-Template Matching
With the 2004 release, we have added a multi-template matching feature. Template matching supports the detection of any pre-selected pattern on a user interface, including non-textual areas, regardless of the target location. The multi-template matching feature increases matching accuracy when there are multiple candidates for an image pattern on the screen.
Multi-template matching provides a way of identifying the location of the target image pattern at runtime which doesn't depend on precise coordinates: using a reference label specified through the "Labelled By" property.
In the example screen below, we want to target the checkbox template that’s labelled by "Checkbox7". At runtime, the correct checkbox is identified by means of this label, even though there are multiple hits.
OCR Neighboring Controls Text Match
Using item coordinates at design time to identify text items on an application page doesn't always deliver the required results. That's because page layouts at runtime can vary. With the 2004 release, you can now choose to use the nearest matching text along the x or y axis or a combination of both. You can configure this on one or both of the following item properties:
- Nearest match along width (%): The value represents a deviation margin percentage compared to the width of the application page (screen). At runtime, the nearest text along the x-axis is matched.
- Nearest match along height (%): The value represents a deviation margin percentage compared to the width of the application page (screen). At runtime, the nearest text along the y-axis is matched.
For both properties, the value can range between 0 and 100. The default value is 0, meaning that this feature is disabled. If the deviation at runtime is greater than the configured percentage value, the text is not recognized.
Improvements to Cloud Components
Store
Improvements when getting a package from the Store
If the name of a package is changed during the acquisition, this is now shown in the Factory‘s Acquisitions view.
Additional bots
12 new additional bots are now available in the Store with the 2004 release of SAP Intelligent RPA.
Improvements to Cloud Studio
New UI layout
The user interface of the Cloud Studio has been redesigned to make it more intuitive.
User tasks improvements (2003)
The User Tasks interface was improved in the 2003 release. Creation of user tasks has been simplified: There are no longer optional headers or footers, and a new title component is now available.
Cloud Factory - New Behavior
New tabs: Agents and Environments
The top-level tabs in the Cloud Factory have been changed in the 2004 release: The Deployments and Management tabs have been replaced by new Agents and Environments tabs.
On the Environments tab you manage the packages, triggers, variables and agents used in your environment. You also manage access rights to your environment.
On the Agents tab, you monitor your agents in the Agents section and organize them by machines or users in the Agent Groups section.
Agent groups
With the new Agent groups concept, you organize the agents available in your organization. It replaces the former hierarchy variables. You can group your agents according to two criteria: groups of machines and groups of logins.
Adding an agent or an agent group to an environment links agents to an environment so that packages/jobs can be distributed to them. To select the agents used in an environment, you now use the Environments tab.
Environments
The new Environments tab is the entry point to the Cloud Factory: This is where you define and edit the functional landscapes in which your automation (scenario or process) is deployed and executed.
Environments form a shell grouping all of your project's resources in one place: triggers, packages, variables, and agents.
Trigger wizard
With the 2004 release, the deployment of packages now takes place behind the scenes. A trigger wizard is directly launched from the Packages tab: An “Add Triggers” button replaces the previous Deploy button.
The new trigger wizard also provides an option to minimize the number of package versions per environment.
New package versioning and lifecycle management
With the 2004 release, the package versioning has been improved to solve existing limitations. Inspired by the classic software release mechanism, the versioning scheme of the packages is now:
[Major_Version].[Minor_Version].[Build_Version]
The Major version indicates important modifications potentially leading to incompatibility between versions. The Minor version indicates smaller modifications and bug fixes. The Build version indicates technical information and how many times a package has been generated.
The package is displayed in the Factory as follows: Version 1.0 (Build 1). Only the build version value increases with each update. For example, the second build of Version 1.0 (Build 1) is Version 1.0 (Build 2).
Each released package version has a unique major.minor pair.
Lifecycle management of packages has also been improved with the 2004 release. Changing a package version is the recommended approach to upgrading your deployed packages. With this approach, changing a package’s version doesn't remove previously assigned triggers.
Visual assistance and error management for environments
In an environment, packages and triggers are distinguished by colors indicating their status: blue (enabled), gray (disabled) and orange (for triggers, when the associated package is disabled or in error).
The UI of the environments also displays any errors, including deployment errors.
Improvements for authorization and sharing
You can now share an environment and its rights with other users. All the resources of an environment (agents, variables, packages and triggers) also inherit the rights of this environment.
With the IRPAProjectMember role you can now create environments. If you’ve been granted read access, you can also see the list of agents within an environment.
That’s all for the 2004 release. As usual, some technical improvements have also been introduced. Don’t forget to browse our community and our help portal for further information. Stay tuned - and happy bot-building!
Best,
Guillaume on behalf of SAP Intelligent Robotic Process Automation Team
Learn More
For more information on SAP Intelligent RPA:
- Visit our web page
- Explore successful use cases
- Read blog posts on Intelligent RPA
- Engage with our Community
- Follow us on Twitter, LinkedIn, and YouTube
5 Comments
