I would like to propose a feature that could simplify the maintenance and restructuring of libraries in UiPath Studio, especially for projects that involve many activities. Currently, activities in libraries are strongly dependent on their file paths. This creates challenges when restructuring or moving activities to new folders, as all processes using these activities must be manually updated with the new activities.
Proposal:
Introduce a mechanism where each activity is assigned a unique ID (UUID or GUID) upon creation, allowing activities to be referenced by this ID rather than their file path. This unique ID could be stored in a central configuration file, such as project.json, and automatically managed by UiPath Studio when activities are moved. This would enable restructuring of libraries and folder hierarchies without breaking existing processes, as activities could be identified by their unique ID regardless of their location in the file system.
Benefits:
- Reduces the risk of process failures when libraries are restructured.
- Simplifies maintenance and updates for large library projects.
- Minimizes the need for manual updates to processes when folder structures change.
This feature would save time and enhance workflow efficiency in maintaining large-scale library packages.