Repository organizes Mappings, Sessions, Workflows and Connections. A Domain is a top-level grouping; a Folder belongs to one Domain. Location alone does not grant permissions. Purge contents and Delete are different operations: the former clears the reviewed scope while preserving the selected location; the latter removes a location only when blockers are resolved.
Before you begin
Confirm tenant and location-management permissions. Review dependencies and open editors before deletion. Use a synthetic structure and preserve any information you still need outside the scope being purged.
Procedure
- Select the correct Domain. Create a recognizable Folder and check its path before saving objects.
- Use the available All, Mappings, Sessions, Workflows, Connections or Shared views to identify content by type and identifier.
- To clear a location, open Purge contents from its menu. Review the preview and blockers: its scope can include Mappings, Sessions, Workflows, drafts, Connections, saved versions and child folders.
- Type the requested name exactly and select the acknowledgment. Submit once and wait for the verified result.
- If the response is uncertain, use Check result. Do not repeat the purge until the earlier result is resolved. A stale preview requires Refresh and fresh confirmation.
- If the location must also be removed, use Delete separately. A Domain containing Folders or a location containing artifacts remains blocked.
Verify the result
Check that only reviewed content was removed. The selected location and execution history are preserved. If you subsequently removed an empty location, confirm its absence from the tree. A filtered grid without rows does not prove there are no dependencies.
Errors and recovery
Protected locations or inactive folders have restrictions. Resolve a blocker through supported actions rather than editing stored records. Distinguish a loading failure from an empty inventory. Purge does not promise undo or automatically delete its target Domain.
Synthetic example
Create Training/CustomerDemo and save m_CustomerNames there. In a disposable laboratory, review Purge contents for CustomerDemo and cancel before confirmation if you are only learning.
Verification scope
Use synthetic data and the role authorized for the task. Compare a visual confirmation with the saved record or relevant attempt. Retain only safe identifiers and messages for support; do not share secrets, personal information or tenant data. If an operation outcome is uncertain, check its state before repeating it.
Environment context
Before using this module, confirm Tenant, Domain and Environment in the user menu. The initial environment is Development. Module, Domain and environment capabilities apply together; Production is read only without explicit authorization. Switching the selector does not move artifacts or publish or execute their data. See environments and recovery and environment promotion.
Recover a failed load
If context or inventory cannot load, Repository shows “Repository could not be loaded. Try again.” and a Retry action to query the same authorized context again. Check the connection and selected Tenant, Domain and Environment. A load failure does not mean the repository is empty or that a Trial has lost artifacts. Do not recreate locations or delete drafts to resolve a read error.
Expired temporary drafts are excluded from inventory without turning the context query into a write inside its snapshot. Saved artifacts and existing publications are preserved. If the problem continues, give support the time and HTTP status, without credentials or tenant data.
Retry retains the failed query’s Tenant, Domain and Environment; it does not switch environment or substitute another inventory. If you lack workspace access, open an authorized workspace from the user menu before continuing.