Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Requesting a Robotic Automation translator

Updated on September 10, 2021

Translators allow Pega Robotic Automation to interact with specific technologies and controls, for example; an Infragistics UltraGrid or UltraToolbar control. While Pega Robotic Automation includes translators to support many common technologies, you might encounter an unsupported technology for which an additional translator is required. The process for handling requests for a new translator is outlined below.

At the beginning of a Robotic Automation development project, interrogate the applications that you want to automate to see if new translators are required. Submitting translator requests at the beginning of a development project helps you avoid delays later in the project life cycle.
  1. Create a support request at Pega Support that describes the technology or control that you need. When you request that the Pega Robotic Automation team create a translator, ensure that you supply the following information:
    • Details about the computer environment in which the target application runs.
    • Information about the target application and controls that you want to interrogate.
  2. The Robotic Automation Support team performs the following tasks.
    • Determines if there are existing options for working with the technology so that project development can proceed unhindered.
    • Contacts you to gather details about the requirements, such as the use cases and the properties, methods, and events that you require. When defining requirements, focus only on what is needed to accomplish the current task in your project.
    • Collects application logging information and creates a translator request for the Robotic Automation Development team.
  3. The Robotic Automation Development team reviews the information, determines the feasibility of the translator, and might request additional information. Based on this information, the Robotic Automation Development team estimates the level of effort in man-days and the cost, if any, of developing the translator. During development, the Robotic Automation Development team might provide you with prototypes of the translator to confirm that the functionality meets your needs. Once you approve the prototype, the Robotic Automation Development team finalizes the code so that it is ready for distribution in a future release.

The amount of time that is required to create a translator varies depending on the technology involved, developer availability, and current backlog. Typically, the initial research and level of effort (LOE) estimate can take up to four man-weeks. Creating a translator often requires eight man-weeks once it is added to the development cycle and work begins.

Note: Once work begins, Robotic Automation developers often require additional information and feedback. Your timely response is critical for keeping the development effort on schedule.
  • Previous topic What causes an Agile Desktop Fatal Application Error?
  • Next topic Understanding how the Citrix Context works with the Citrix ICA file

Related articles

Attachment: Creating UI Connectors


Robotics System Architect Robotic Process Automation

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us