Existing directory structure
legacy-txhyperautomate-uipath/
└── .objects/
└── -huLR/
├── .data/
│ └── ObjectSelectionName/
│ ├── .content
│ └── .hash
├── ffb8/
│ ├── .metadata
│ ├── .type
│ └── 94v5/
│ ├── .data/
│ │ └── ObjectRepositoryScreenData/
│ │ ├── .attributes/
│ │ ├── .images/
│ │ ├── .content
│ │ └── .hash
│ ├── .metadata
│ ├── .title
│ └── SZL0/
│ ├── .data/
│ │ └── ObjectRepositoryTargetData/
│ │ ├── .attributes/
│ │ ├── .images/
│ │ ├── .content
│ │ └── .hash
│ ├── .metadata
│ └── .title
├── .metadata
└── .type
Existing locator hierarchy
xisting Locator Hierarchy
Leve Object Type Description Physical Mapping
l
1 UI Edge [Link] Corresponds to top-level alphanumeric
Application join amazon prime folders (e.g., -LFR, PyNF) containing
(Top Level) .metadata and .type files.
1.0.0 – Represents the
application/browser and
its version.
2 UI Screen Edge [Link] Corresponds to middle-tier folders (e.g.,
(Middle join amazon prime – eSxy) containing the
Level) Represents a specific ObjectRepositoryScreenData
window, tab, or page directory with screen-specific
state. screenshots and attributes.
3 UI Element SPAN – Represents an Corresponds to the deepest nested
(Leaf Level) individual UI control such folder (e.g., JzYB) containing
as a button, textbox, or ObjectRepositoryTargetData with
HTML element. selectors, image snippets, fuzzy logic,
and hashes used for identification.
Folder-Level Mapping
# Action Performed Observed Impact
1 Delete 94v5 folder Removes UI Screen and its child UI Element.
2 Delete ffb8 folder Removes UI Screen and its child UI Element.
3 Delete SZL0 folder Removes only the UI Element.
4 Delete -huLR/.data No visible effect; folder gets regenerated automatically.
folder Behavior is ambiguous.
5 Delete PyNF/.data No visible effect.
folder
6 Delete 94v5/.data No visible effect; folder regenerates automatically during
folder runtime.
7 Delete SZL0 folder Unable to drag locator from Object Repository.
8 Delete all .data No observable effect.
folders
File-Level Mapping
# Action Performed Observed Impact
1 Delete .metadata and .type No effect on locators.
inside ./objects
2 Delete .metadata inside huLR Removes entire UI Application.
3 Delete .type inside huLR No effect; test case continues to work.
4 Delete .type inside ffb8 No effect.
5 Delete .type inside 94v5 No effect.
6 Delete .type inside SZL0 No effect.
7 Observe .data folder generation .data folders are automatically regenerated
and remain empty.
8 Delete .data inside ffb8 Removes UI Screen.
9 Delete .metadata inside 94v5 Removes UI Screen.
10 Delete .metadata inside SZL0 Removes UI Element.
Inferred Repository Structure
Repository Likely Folder/File Dependency
Object
UI Application Folder + .metadata
UI Screen Folder + .metadata
UI Element Folder + .metadata
.type files Appear non-critical; deletion has no visible impact.
.data folders Mostly cache/runtime-generated; limited functional impact except
observed case in ffb8.
Folder existence Critical; deleting object folders removes corresponding repository
objects.
.metadata files Critical; deleting them removes the associated repository object.
Final directory structure
└── legacy-txhyperautomate-uipath/
└── .objects/
└── huLR/
├── ffb8/
│ ├── 94v5/
│ │ ├── SZL0/
│ │ │ ├── .data/
│ │ │ │ └── ObjectRepositoryTargetData/
│ │ │ │ └── .content (File)
│ │ │ └── .metadata (File)
│ │ └── .metadata (File)
│ └── .metadata (File)
└── .metadata (File)