Operating a website with browser steps (RPA)

In the portal, under Environments, click Development, and there Open. Create a new workflow in the module General.

In the library the browser steps are grouped under Browser (RPA). Start with Browser session: an area in which all steps share the same browser — the same sign-in, the same page. After the area, the browser closes.

Browser steps run in a browser of their own next to the environment, shielded from everything else. If that is still off, the step says so itself, with what it costs. As an owner you click Switch on: the portal opens at that one switch and you confirm with Switch on. It applies to every environment of your organisation at once; each environment starts again in the background with a browser of its own. If you are not an owner, it says Ask the owner: the owners get your request in the portal and by e-mail.

Only the sites you list here can be reached; every other request the page makes is blocked. Start at is the page where the browser opens. Screenshots after every step are on by default. Then connect the trigger to the session.

With Add step in the area you choose Fill in. You point at the field the way a person sees it: by its label Customer number. That way the step keeps working when the site's layout changes.

A Click step on the button named Search: role button, name as written on the button. The step waits by itself until the button is there.

Read table turns a table on the page into a list: one item per row, with the column headings as fields. Store it as invoices; next steps (a loop, a Flow table) simply carry on with it.

Inside the area the steps run in the order of their connections: fill in, click, read.

Flow opens the browser, goes through the steps and closes it again. At the bottom you see every step; the invoices are in the data after the run.

Screenshots in the toolbar shows per step what was on the screen. Fields you mark as secret (a password) are blacked out. When a step fails, Flow also keeps a trace to replay it.