Using folder-level entities in Studio Web

Data Fabric entities are fully integrated with Solutions, eliminating the need to manually recreate entities during package deployment.

Only the entities created in a folder can be used in solutions, where they will be available as a solution resource.

Automatic resource inclusion

• When a folder entity is used in a Solution, it is automatically added as a Solution resource.
• Manual entity recreation steps previously required during deployment are not necessary for folder-level entities.

Packaging and deployment

• When a package is deployed to a folder, any required entities are created automatically:
  • Folder-level entities are created in the target folder.
  • Tenant-level entities, if not already present, are created at the tenant level if packaged via Orchestrator.
• Tenant-level entities used in a workflow are not automatically packaged or published — they must already exist in the target environment for the deployed workflow to function as expected.

Studio Web behavior

• When using Data Service activities in Studio Web, select the folder entity scope for the entity context.
• Only entities from folders where the user has access are displayed.
• Folder-level entities used in workflows are automatically added to the Solution.

Deployment and debug options

Override is supported at two stages: during debug, when a workflow is being built in Studio Web, and during runtime, after the workflow is packaged, deployed, and the RPA process is being executed.

During debug - the entity used can be kept as-is, replaced with a different existing entity, or removed entirely. If the selection is removed, a new entity, along with its dependencies, is created in the Personal Workspace to support the debug execution.

During runtime - the override options are limited: the workflow can run on the existing entity or be mapped to a different existing entity. Creating a new entity at runtime is not supported.

Entity relationships

If Entity A is related to Entity B, both entities are automatically added as Solution resources.

Override is only available for resources directly referenced from an activity. By default, this applies to Entity A. Entity B is not eligible for override unless it is referenced directly from an activity via Platform resources, not Defined resources.

Observação:

• In both cases, the override functionality allows entities used in a workflow to be mapped to existing entities with a compatible schema from a different folder.
• Mapping across tenants is not supported.
• When using override during debug and runtime, ensure the replacement entity maintains the required relationships to avoid schema mismatch errors.

Supported scenarios

• Data Service activities in Studio Web.
• Studio Web-based automation workflows.
• Apps (VP Apps) using Data Service tenant entities.