Skip to main content

Integration Service-based activities release notes

View the release notes for the Integration Service-based Data Service activity package.

March 3, 2026​

Introducing the Query Multiple Entity Records activity​

Query Multiple Entity Records, a new Data Fabric activity, is now available.

The new activity allows you to:

  • query two entities in a single activity;
  • apply joins (Inner or Left) between the two entities;
  • work with combined data results in a single output;
  • use the output directly in workflows, Apps, or downstream logic.
note

The Query Multiple Entity Records activity is automatically available when the Database Hub external system is enabled.

To enable the Database Hub external system, you have to raise a ticket with our support team.

For more information, refer to Query Multiple Entity Records.

February 24, 2026​

Filter builder for the Query Entity Records activity​

The Query Entity Records activity now includes a built-in filter builder, so you no longer need to manually enter CEQL expressions.

Removed suffix from all Integration Service - based activities​

We have removed the (New) suffix in all the Integration Service - based activities names.

Integration Service - based activities availability​

Integration Service - based activities are only available in Maestro, API workflows, and agents where traditional Studio activities are not available.

February 19, 2026​

Security improvement​

We've made a security improvement that performs RBAC validation prior to Data Fabric event delivery, using the exact user identity configured on any of the following trigger connections:

  • Workflow automations
  • Agentic processes (Maestro)
  • RPA workflows
  • API workflows

Data Fabric events are delivered only if the connection user has read access to:

  • the target entity;
  • all RBAC-protected fields in the payload.

The following table presents the impact of whether or not the required permissions are assigned to the connection user:

ScenarioData Fabric event deliveryWorkflow
The connection user has the required entity- and field-level permissionsDeliveredExecutes as expected
The connection user is not assigned entity-level permissionsNot deliveredIs not triggered
The connection user is not assigned field-level permissionsDelivered with restricted fields removed from the payload before deliveryMay behave unexpectedly

To ensure proper event delivery, choose one of the following options:

  1. Update permissions

    a. Identify the trigger connection and its user. b. Assign the connection user read access to the target entity and all RBAC-protected fields referenced by the workflow. For more information, refer to Managing access.

  2. Reconfigure connection

    a. Create a connection with a user account that has the required entity- and field-level read permissions. b. Update the workflow trigger to use the newly created connection. c. Redeploy or republish the workflow.

note

Before deploying to production, perform a dry run of the workflow using the Debug feature.

For RPA workflows only, you can also use the design-time Test Trigger with the intended connection identity to verify permissions before production.

For more information refer to UiPath Data Fabric events and Triggers.

December 16, 2024​

Unified Data Service activity package​

Data Service activities are now delivered through the unified UiPath.IntegrationService.Activities package.

To use these activities, create a connection to UiPath Data Service through the new Data Service connector in Integration Service.

This integration brings new event-triggering capabilities and greater interoperability with other UiPath products, facilitating more complex end-to-end automation scenarios. The unified package offers feature parity with all the existing activities from the Data Service activity package, though some have been renamed.

The UiPath.IntegrationService.Activities package is always displayed in Studio, in the Activities panel, in the Available section. To install any activity, drag and drop it into the canvas (in Studio Desktop) or add it to your workflow (in Studio Web).

You do not have to manually update the package. As part of UiPath Automation Cloud™, the activity package updates automatically.