Robotic Process Automation
Robotic Process Automation (RPA) in the Analog Informatics Corporation (AIC) AIC Enterprise Privilege Suite™ drives a web management console the way an administrator would, then records the run. Use it for printers, baseboard management controllers, network appliances, storage arrays, and software consoles that expose a web page and no application programming interface (API).
The password stays in the privileged vault. A workflow names the fields. At run time the suite fills the account, the current password, and the new password. The workflow definition does not contain the password.
RPA is available now as part of Privileged Identity Management in AIC Enterprise Privilege Suite™. See Privileged Identity Management and Capabilities.
Short answers
What does RPA do? It opens a web console, signs in, changes a credential or reads a value, and stores the result of the run.
Where do I work? The console has four places: Workflows, Builder, Recipes, and Executions.
What ships ready to run? Generic sign-in, a generic web password-change form, Dell iDRAC 9, HPE iLO 5, Xerox printers and multifunction devices, and export of accounts from another privileged-access web console.
Can I add a device the suite has never seen? Yes. Start from a recipe or a blank workflow, test it on one device, publish it, and run that published version on the rest.
What is kept after a run? The workflow, the version, the system, the account, who started it, and whether it is pending, running, succeeded, or failed. A failed step can keep a screenshot. You can also name screenshots to keep when the run succeeds.
Workflows, recipes, and executions
| Surface | What you do there |
|---|---|
| Workflows | List every workflow, open one version, publish it, deprecate it, or delete it |
| Builder | Add steps from a palette, reorder them, and save. The same definition can be edited as JSON |
| Recipes | Browse the built-in workflows and open one as the starting point for a device you manage |
| Executions | See each run, and filter by workflow, job, or system |
A workflow has a name, a version, a platform type, the variables the run must supply, and an ordered list of steps. Only one version of a workflow is published at a time. Older versions stay as deprecated. A draft cannot be the version a job runs.
Steps you can put in a workflow
Each step is one building block. A step can set its own timeout and how many times to retry.
| Group | Steps |
|---|---|
| Open the page | Go to an address, wait for the page to finish loading, read the current address |
| Use the page | Click, type, clear a field, focus a field, hover |
| Read the page | Wait for an element, read its text, read an attribute, check that an element is present, read the page title |
| Keep evidence | Screenshot, Portable Document Format (PDF) of the page, full HyperText Markup Language (HTML) |
| Check and wait | Pause, assert that an element exists, assert that its text contains a phrase |
| Sign in | Fill the username field, the password field, and the submit button, then wait for the next page |
Selectors are Cascading Style Sheets (CSS) selectors. Variables in a step are replaced when the run starts. The password is one of those variables. It is not stored in the workflow.
How the suite reaches the page
| Path | When it is used |
|---|---|
| Plain HTTP | The page is a simple form. No browser is started |
| Headless browser | The page needs JavaScript. The suite drives Chrome through the Chrome DevTools Protocol |
| Automatic | Try plain HTTP first. If the page depends on JavaScript, use the browser |
A password-change job for a web-only device runs the published workflow for that platform and records the execution against the job, the system, and the account.
When a step fails
| Policy | What happens |
|---|---|
| Screenshot and fail | Save a screenshot of the page, then stop the run. This is the default |
| Abort | Stop the run |
| Continue | Record the failed step and go on to the next step |
Execution status is pending, running, succeeded, or failed.
Ready-made recipes
| Recipe | What it does |
|---|---|
| Generic login | Open a web console, sign in with a form, and take a screenshot |
| Generic password change | Sign in, open the password form, fill the current and new passwords, and submit. Copy it when a device uses a standard form |
| Dell iDRAC 9 | Sign in to the iDRAC web console, open the user, and change the password |
| HPE iLO 5 | Sign in to the iLO web console, open user administration, and change the password |
| Xerox | Sign in to the printer or multifunction web console and change the administrator password |
| Account export | Sign in to another privileged-access web console and export the account list |
Built-in recipes are compiled into the product. A workflow you write is stored with your other workflows and follows the same draft, publish, and deprecate path.
Related pages
Copyright 2026 Analog Informatics Corporation. All rights reserved.
For more information about Analog Informatics Corporation, please go to analoginfo.com.