Updated Nov 5, 2026
3 min readDocument imports: the file is only half the test.
A successful upload does not prove that a document belongs to the right revision. A practical verification path for Active Workspace customizations.
PLM Nexus technical team
- Target revisionThe right business object
- Dataset relationshipThe intended document role
- Stored resultContent and metadata checked
Process diagram
Our Active Workspace work for SACMI included adapting a document-import customization, functional checks and handover. The guidance below presents a general approach to verifying document imports.
Start with the relationship, not the button
Write down the source revision, dataset type, relationship and expected metadata before changing the interface. These identify what the command must preserve. A visible file is not enough if it is attached to the wrong object or through the wrong relationship.
A small, useful test matrix
For a similar customization, plan four checks: the supported revision and file type; an unsupported selection; a repeated import; and a user without the required permission. Define the expected result before running each one. These are recommended checks, not a claim that every scenario was executed in the historical assignment.
After the operation, reopen the revision and inspect the dataset, relationship and properties. Check the stored result as well as the success message. If a failure leaves a partial result, make that state visible and agree how it will be recovered.
Make the handover reproducible
Record the target AWC version, configuration, starting selection, expected result and observed result. Keep this record with the customization. A future maintainer can then distinguish a changed business rule from a regression introduced by the next port.
These are proposed acceptance checks, not completed tests or customer results. Set the expected behavior with the process owner, record the environment and version, then fill in the observed result and evidence. Blank cells are not passes.
| Scenario | Expected result | Evidence to retain |
|---|---|---|
| Supported import | File, dataset, relationship and revision match the agreed target. | Object IDs, relation and reopened file. |
| Unsupported selection | Clear rejection; no unintended objects created. | Message and before/after object list. |
| Repeated import | Agreed update, new version or rejection; no accidental duplicate. | IDs and versions after both attempts. |
| Insufficient permission | No permission bypass; any partial result is identified. | Test user, denied action and stored state. |
| Interrupted operation | Partial state is visible; recovery or retry has a defined outcome. | Failure point, object state and recovery evidence. |
Next step
If this pattern is showing up in your Teamcenter environment, explore the relevant service or discuss the change you need.