Pega Robotic Automation API

General
, , , ,
1

Pega Robotic Automation™ can support Pega Platform™ by automating front-end applications without accessible Pega Platform channels by using the right tool for the right time. For example, if an application has an API, Pega Platform can access the application API. If the application does not have an API, then Pega Robotic Automation can access the application for use in the case life cycle.

Above is taken from Pega academy.

I just want to understand.

Are they saying If an application on the Pega platfrom has an API it can not be used by Pega RPA? but if the app does not have an API its open for use by Pega RPA?

Way it was worded is hard to understand can anyone shed some clarity on this.

Thanks

2

@DavidA4231 could you provide the URL for the Pega Academy mission where you see the above description about Pega Robotic Automation vs Application API?

Once I can identify the author I’ll be able to check for you.

3

Hi @DavidA4231 please go through below information to get some clarity about your question

Understanding Pega API and Pega RPA

  1. Pega API:
    • APIs (Application Programming Interfaces) are used to allow different systems to communicate with each other programmatically. Pega provides various APIs to interact with its platform, enabling integration with other systems.
  2. Pega RPA:
    • Pega RPA is a tool that automates repetitive tasks by mimicking the actions of a human interacting with the user interface of an application. This includes interacting with web pages, desktop applications, and other UI-based interfaces.

Key Points:

  1. Application with an API:
    • If an application has an API, it means the application exposes its functionality through endpoints that can be called programmatically.
    • This does not mean that Pega RPA cannot be used with the application. In fact, having an API might provide an alternative, often more efficient, way to integrate or interact with the application.
    • Pega RPA can still be used to automate tasks in applications that have APIs, but often, leveraging APIs directly (using Pega’s integration capabilities) can be more efficient and reliable than UI-based automation.
  2. Application without an API:
    • If an application does not have an API, it means that there’s no programmatic interface available for direct integration.
    • In such cases, Pega RPA becomes a valuable tool because it can automate interactions with the application’s user interface, effectively bypassing the need for an API.
    • Pega RPA can be used to perform actions such as data entry, navigation, and other repetitive tasks within the application by simulating user interactions.

Practical Considerations:

  • Using API over RPA:
    • Whenever possible, using an API for integration is generally preferred because it is more reliable, faster, and less prone to errors compared to UI automation.
    • APIs allow for more direct and granular control over application functions and data.
  • Using RPA for Non-API Applications:
    • RPA is especially useful for automating tasks in legacy applications, applications with no APIs, or scenarios where APIs are not feasible or available.
    • RPA can also be used in conjunction with API-based integrations to fill gaps where UI interactions are still necessary.

Summary:

  • Applications with APIs: Pega RPA can be used, but direct API integration is usually preferred.
  • Applications without APIs: Pega RPA can be used and is often the best or only option for automation in such cases.

In conclusion, Pega RPA is versatile and can be used regardless of whether an application has an API