AWC debugging is different from normal UI debugging because many problems are not in custom code. They are in ctx, declarative JSON, service payloads, or wrong assumptions about the selected object.
Best debugging order
- check selected object in ctx
- inspect ViewModel JSON and condition logic
- verify the service call and response payload
- confirm property mapping and data provider output
- validate panel and command visibility conditions
1. ctx
Is the correct object selected? Are you on item or item revision?
2. ViewModel
Do commands, conditions, and data providers point to the right state?
3. Service
Does the service return the property and object type your panel expects?
Common bugs
- button not visible for one object type only
- panel opens but shows empty values
- wrong object data displayed after selection change
- works in one environment but not another because config differs
Practical rule
Always debug ctx first.
If ctx is wrong, the rest of the UI flow usually becomes misleading.