Active Workspace (AWC) is not just a screen on top of Teamcenter. It is the interaction layer through which users search, open, edit, review, and navigate product data.
What is AWC really?
AWC is the modern web client of Teamcenter. Users use it to interact with product structures, workflows, documents, changes, and lifecycle data without depending on the classic rich client experience.
UI ComponentsPanels, commands, tables, forms, object pages
↓
Declarative ViewModelConditions, actions, data providers, command config
↓
ServicesSOA / REST calls into Teamcenter business logic
↓
Teamcenter DataItem, Item Revision, BOM, Workflow, Change, Dataset
Why developers must understand AWC
- UI issues are often not frontend-only issues
- many behaviors are driven by configuration, not only code
- ctx, ViewModel, and service responses decide what users actually see
Core concepts you must know
ctx
Application context. It stores selected object, user state, and current application state.
Declarative UI
Buttons, panels, commands, and visibility are often configured by JSON-style definitions.
Services
AWC asks Teamcenter for data through service calls, then renders the response.
Why UI sometimes shows wrong data
- wrong ctx binding
- incorrect selected object assumption
- wrong property mapping in declarative config
- service returns one object, panel expects another