Recording automations

  • Release version: Australia
  • Updated June 18, 2026
  • 3 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Recording automations

    The recorder option in the RPA Desktop Design Studio application allows ServiceNow customers to capture actions performed on desktop or web applications and automatically convert them into an automation flow. This feature supports both attended and unattended automations and eliminates the need to manually build automations using connectors or components. It is designed for applications compatible with the Universal App Connector, enabling precise element interrogation.

    Show full answer Show less

    Key Features

    • Element Highlighting: Differentiates types of elements within applications to facilitate selecting appropriate actions.
    • Recorded Actions Pane: Displays captured actions organized by application screens, showing the action type and target elements.
    • Automation Flow Generation: Upon saving a recording, an automation flow is created as an activity within the project and configured as a global object for reuse and further enhancement.
    • Screen Match Rules Configuration: Users can customize screen and element attributes using the Universal App Connector to improve accuracy.
    • Automatic Element Naming: Element names are auto-filled from the target application during recording, improving clarity and reducing manual input.
    • Rearranging and Editing Actions: Recorded actions and screens can be reordered in the Recorded actions pane, which updates the generated automation flow accordingly. Actions can also be edited directly to change element details or action types without re-recording.
    • Automatic Application Launch Component: The automation flow includes a launch application component automatically, streamlining setup.

    Benefits

    • Enables low-code users to build automations quickly and easily without deep technical knowledge.
    • Reduces the time and effort required to create automations compared to manual connector or component setup.

    Practical Considerations

    The recorder supports only applications interrogated via the Universal App Connector. Customers should be aware of known limitations detailed in the RPA Desktop Design Studio documentation. The recording captures actions on various element types such as text boxes, buttons, and hyperlinks, which can then be used to build comprehensive automation flows.

    Next Steps

    ServiceNow customers can start recording automations by using the recorder in the RPA Desktop Design Studio application to streamline automation creation. They can further refine and customize the generated flows on the design surface, configure screen matching rules, and edit recorded actions to tailor automations to their specific needs.

    Capture your actions from your desktop or web applications and convert them into an automation flow by using the recorder option in the RPA Desktop Design Studio application. You can record attended and unattended automations by using this capability. When you record an automation, you don't have to create it manually by using connectors or components.

    Important:
    The recorder feature supports the applications which can be interrogated using the Universal App Connector.

    Highlighting an element

    When you use the recorder, you can highlight the different elements in an application. These highlights enable you to differentiate the different type of elements. You can then perform the required action for each element. Each element has a default action and a list of sub-actions.

    Figure 1. Highlighting an element by using the recorder
    Highlighting an element when using the recorder.

    Recorded actions pane

    The action that you perform on each element is captured in the Recorded actions pane. The recorded action in the Recorded actions pane displays the type of action and the element on which the action is performed. The recorded actions are also listed according to the application screens.

    Automation flow generation

    When a recording is saved, the RPA Desktop Design Studio application generates an automation flow as an activity to the automation project. The recording is also automatically configured as an object and listed under the Global Objects option in the Project Explorer pane. You can improve the generated automation flow from the Design surface by adding further components.

    Configuring the screen match rules

    The screens and elements of the recording are also configured as objects to Global Objects. You can configure the screen match rules and the element attributes based on your preference, by using the Universal App Connector. For more information on how to use the Universal App Connector, see Universal app connector.

    Enhanced element interrogations

    Populate element name

    When you record an action in the application, the element name is automatically filled in the Recorded actions pane. The element name is captured from the target application. In the following example, while recording the SendKeys action, the element name "Location" is automatically filled, followed by "with text" and the keys or text value that is inputted by the user during the recording phase. If no default element name is available in the target application, the type of element is used as the name.

    Figure 2. SendKeys Action type
    SendKeys action on element name "Location".

    Rearrange recorded actions

    You can move and position your recorded actions and screens in the Recorded actions pane. You can also rearrange recorded elements in the Recorded actions pane. The recorded screen segment is split when a recorded action from a screen segment is dropped on to a different screen segment.
    Figure 3. Rearranged elements in the Recorded actions pane
    Rearranged elements in the Recorded actions pane.
    For example, when you record two actions of the QUOTES SYSTEM application, (DoubleClick and Click) and two actions of the Badge Tool application (Focus and GetText). Then, the list of actions are displayed in the Recorded actions pane, in the order in which they are recorded.
    Figure 4. Actions in the Recorded actions pane before rearranging
    Actions in the Recorded actions pane before rearranging.
    When you move the Focus action from the Badge Tool application to the top of the list and above the QUOTES SYSTEM application. Then, the list of actions are displayed as follows in the Recorded actions pane, after the hierarchy is rearranged. The recordings of the QUOTES SYSTEM application are split.
    Figure 5. Actions in the Recorded actions pane after rearranging
    Actions in the Recorded actions pane after rearranging.

    When you save the recording, the automation is generated accordingly. The automation flow is generated based on the new sequence of actions in the Recorded actions pane.

    Editing a recorded action

    Instead of deleting and re-recording an action, you can update the action type or element details by editing the recorded action, using the Edit action icon, in the Recorded actions pane. For example, you can edit the "GetText" action type on "About" element name in the following image.
    Figure 6. Edit a recorded action
    Edit action on the Recorded actions panel.
    After selecting the edit action, you can change the action type to "SetText" or element name to "Tools" from "About" and select Update, as shown in the following example.
    Figure 7. Update the recorded action after editing
    Select the Update button after editing the recorded action.

    Launch application

    On the design surface, the component to launch an application is now added automatically to the automation flow that is generated by the recorder.

    Benefits of creating automations with the recorder

    Using a recorder to create an automation provides the following benefits:
    • Low-code users can create automations more easily. Manually creating an automation with a connector or component is complicated.
    • There's less time and effort needed to create an automation with the recorder.

    Limitations

    For information on the known issues and limitations for recording automations, see Known issues and limitations of RPA Desktop Design Studio for recording automations [KB1225708].