Holding Area
UI: Holding Area
Purpose
Validation area for uploads that failed naming standard / attributes and are not yet ready in the main CDE.
Relevance
Prevents clutter in Files. Empty state: “All uploads are compliant” — if you're here, corrections need to be made before federating or transmitting.
Usage Example
After upload, 3 IFCs are Invalid - correction needed. The BIM manager enters Validation Mode, edits fields (or AI Fill), Commits; those that do not meet the naming standard remain in the holding area.
Who can use it
CDE users with validation/holding permissions.
Screen Anatomy
- List mode (browse) vs Validation Mode (edit + Commit).
- Stats: Total · Valid · Invalid · Selected · Pending changes · Ready to send.
- Document grid; pagination (Rows per page).
- Ribbon according to the mode.
Options and Fields
Ribbon
| Mode | Actions |
|---|---|
| List | Validate · Delete |
| Validation | Commit · Cancel · Edit in Batch · AI Fill |
List Columns
Status (Valid / Invalid - correction needed) · Name · Version · Path · Added by · Added to holding area · Naming standard.
Validation Fields (naming tokens / attrs)
Project · Company · Location · Type · Number · Phase · + dynamic attributes from the folder's naming standard.
Editing: Click to edit · Select date · Empty · Multiple values… · Select…
Others
| Control | Function |
|---|---|
| Delete Files | Deletes selection (irreversible) |
| AI Fill / suggestions | Assisted filling — review before Commit |
| Pagination | Navigate pages |
How to Use
- CDE → Holding Area (or follow the toast after upload).
- Validate → enter Validation Mode.
- Correct Invalid (inline / Edit in Batch / AI Fill).
- Commit when Ready to send.
- Confirm in Files; remaining invalid files stay in holding.
Links
Tips / Common Errors
- Empty Holding Area = compliant uploads.
- AI Fill: always verify (“Filled by AI — please verify”).
- Commit does not “force” invalid naming — those files remain in the holding area.
Was this article helpful?