activities
latest
false
UiPath logo, featuring letters U and I in white

Workflow Activities

Last updated Feb 19, 2025

Track Object

UiPath.Core.Activities.ProcessTracking.TrackObjectUiPath.Core.Activities.ProcessTracking.TrackObject

Description

The Track Object activity allows the Process Tracking Scope activity to track a task in an existing trace. In Process Mining, you can analyse data about the objects attached to a task or trace.

The following example describes the steps in an Invoice Processing workflow and how the Track Object activity can help:

  1. Step 1: Receiving an invoice

    • When an invoice is received, you use the Track Object activity to start the invoice (the object) tracking and sent the data to Process Mining. The following properties are set:

      • Object ID: "INV-2025-001"

      • Object type: "Invoice"

      • Object interaction: Create

      • Object properties: {"Vendor": "Acme Corp", "Amount": "5000", "Date": "2025-02-10"}

  2. Step 2: Validating the invoice

    • After validating the invoice details, you use a second Track Object activity to mark that invoice details have been updated:

      • Object ID: "INV-2025-001"

      • Object type: "Invoice"

      • Object interaction: Update

      • Object properties: {"ValidationStatus": "Passed", "ValidatedBy": "AutoBot1"}

  3. Step 3: Processing the payment

    • When initiating payment, you use a third Track Object activity to mark that invoice payment details have been updated:

      • Object ID: "INV-2025-001"

      • Object type: "Invoice"

      • Object interaction: Update

      • Object properties: {"PaymentStatus": "Initiated", "PaymentDate": "2025-02-15"}

  4. Step 4: Final recording

    • After payment confirmation, you use a fourth Track Object activity to update the invoice with its final details:

      • Object ID: "INV-2025-001"

      • Object type: "Invoice"

      • Object interaction: Update

      • Object properties: {"Status": "Completed", "CompletionDate": "2025-02-16"}

Important:

You can connect two automations through the business item or object they both operate with. For example, automation A1 creates the object using the Track Object activity, giving it a name, a type, and the Object interaction is Created. In a separate automation A2, you reference the same object using the Track Object activity, where you use the same object name and type. The interaction for automation A2 is different than Created, as the second automation updates the object. The collected data about the object is sent to Process Mining for analysis.

Project compatibility

Windows | Cross-platform

Windows, Cross-Platform Configuration

Object ID

Mandatory. The unique identifier for the object you want to track. Accepts String data types. For instance, the invoice number "INV-2025-001".

Object type

Mandatory. The category or type of the object. Accepts String data types. For instance, "Invoice", "Document", "Customer".

Object interaction

Mandatory. Specify how the automation interacts with the object. The available options are Create, Read, Update, Delete.

Object properties

Optional. Specify a dictionary of key-value pairs for additional metadata about the object. The available options are Create, Read, Update, Delete.

  • Description
  • Project compatibility
  • Windows, Cross-Platform Configuration

Was this page helpful?

Get The Help You Need
Learning RPA - Automation Courses
UiPath Community Forum
Uipath Logo White
Trust and Security
© 2005-2025 UiPath. All rights reserved.