Capturing your Processes

Please note: We will shut down the Helpdesk soon. Please update your releases to Hyland RPA 22.2. To view the latest documentation for Hyland RPA 22.2 release visit Hyland Docs.

How to Start your Process Documentation

To start Smart Process Tracking, click New in the Start Menu and you will be redirected to the documenting mode. You can open the start screen of the process in your live application that you start with.

For capturing in browser sessions, you should avoid switching between tabs - start new sessions instead. Whenever you will try to start documenting in Chrome, Firefox or Edge Chromium, the Analyst (former Muse) will ask you to confirm opening the browser session again. Accept this in the pop-up to be able to flawlessly recognize elements in browser sessions with Selenium.

Please note! Do not forget to also capture the login process in every application!
Please note! To capture your SAP process you need to activate your SAP Scripting. For further instructions, please click here. You also need to restart the Smart Indicator after reactivating SAP Scripting.

The action bar stays in the foreground at all times, but will not be shown on the screenshots taken by the Hyland RPA Analyst (former AM Muse). To start the Smart Indicator, hit the Start button. You will recognize its activity when hovering over your screen, as colored rectangles appear over the screen elements.

Now you can start indicating and telling the Hyland RPA Analyst (former AM Muse) which actions to perform, e.g., create a left-click action on a button in your live system, choose the corresponding toggle in the action panel and click on the button on your screen. Afterward, you can insert a description into the action list. Entering a detailed description with plenty of information will make it easier to understand and enhance the process later on in the automation journey.

Frictionless Mode

In Frictionless mode, the application detects all user actions, such as clicks and and keyboard input, as actions and captures them in the action panel.

  • The action you performed is recognized, meaning for example a right-click creates a right-click action. The same applies to double-click, left-click and keyboard input.
    The AUTO toggle switches for a few seconds to display the performed action.
  • To capture read-out text buttons, select the Read-out text toggle and capture your element with a left-click.
  • The Frictionless mode is enabled per default. To switch to the Impermeable mode, change the Documenting mode in the Settings.
Please note! You can directly interact with the Analyst (former Muse) interface with an active Smart Indicator - the interface of the Hyland RPA Analyst (former AM Muse) is ignored by the Smart Indicator. This way you do not have to pause and restart the Smart Indicator again after changing an action type or typing in a description.
Please note! If the Smart Indicator is not able to identify the elements you want to capture, please use the snipping function. To do this, press ALT or CTRL key and snip the area you want to capture. An action is then subsequently created in your action list.

This video is based on the former AM products before the switch and rebranding to Hyland RPA.

Key capturing

You can also add keys and hotkeys manually to the action list.


Afterwards, the property pop-up will appear for you to fill in details about the key or key combination.

The other way to capture keys is to let the Hyland RPA Analyst (former AM Muse) detect your key interactions directly during capturing. As soon as the Smart Indicator is turned on and the Frictionless mode is enabled (default setting), all (hot-)key combinations are automatically captured and transferred to (hot-)key actions, as well as specific special key actions.


This video is based on the former AM products before the switch and rebranding to Hyland RPA.

To finish the documenting, simply press Done to go to Editing Mode.

Impermeable Mode

Using the Impermeable mode oo clicks are performed in the documentation environment, no actions detected and no keys are recorded.

Check out our tutorials to learn more about Capturing and Describing your Processes with Hyland RPA Analyst (former AM Muse) using the Impermeable mode.


When to Start and Stop your Process Documentation

This section contains a few tips on how to create better documentation for easier automation:

  1. There is no need to document the steps that describe how to start an application and where to find it on your device. The Hyland RPA Analyst (former AM Muse) detects this automatically.
  2. If logging into a certain application is required, log out before starting so that you can indicate how to start on the login screen.
  3. Do not forget to also capture the closing of an application and, if necessary, the logging out of applications and systems.

Capturing Alternative Process Runs

An often-occurring mistake is to simply capture the “happy path” of a process, which is the path you most often use. However, most likely there are more than one possible course, progression or outcome of a process. Here is an easy example: the process covers copying customer information, meaning multiple entries from one system into the other – copy, paste, easy. But what if the first system is missing one entry that is mandatory for the next system? Because of this, you should also cover the alternative runs of a process and describe what led to the decision of following another process path.

The Hyland RPA Analyst (former AM Muse) allows you to cover every possible process run. To do so, click Done to go to the editing mode, then click on Run Overview to see a list of all captured runs. Here you can add, rename, delete and duplicate runs. Double-clicking on a run in the list and then pressing Start allows you to add documentation to a run.

Please note! You should always cover the entire process in one run, from the beginning to the end, depending on its course.

Here is an easy trick to avoid double work when documenting the start of your process, logins etc.:

  1. Go to the Editing Mode.
  2. Right click on the last window (+actions) of an existing run that is identical to the new one you want to capture.
  3. Click on Start New Run from Here to duplicate the current run up to this point.
  4. Click Start again to start documenting with the alternative run without having to capture the beginning of the process again.

Check also our Tutorials to learn more about Alternative Process Runs in the Hyland RPA Analyst (former AM Muse).

Was this article helpful?
0 out of 0 found this helpful