AWC configuration is where most of the power sits. If you understand how commands, conditions, actions, data providers, and panel definitions work together, you can reason about most UI behavior without heavy custom coding.
Main building blocks
- ViewModel JSON
- commands
- conditions
- actions
- data providers
- panels and placements
ConditionShould this command or panel be visible?
↓
ActionWhat should happen when the user clicks?
↓
Data ProviderWhich data should load and bind into the UI?
Common configuration mistakes
- hardcoding where declarative config should be used
- reusing conditions without checking object context
- mapping properties that are not present in the response
- assuming one object type while panel runs in many places