-
Type: Improvement
-
Status: Resolved
-
Priority: Major
-
Resolution: Won't Fix
-
Affects Version/s: 5.6
-
Fix Version/s: 11.2
-
Component/s: Layouts & Widgets
-
Tags:
-
Backlog priority:405
Current variables exposed by layouts do not resolve the field variable.
Variables exposed in the case of a template widget type could also be useful when defining EL expressions for widget mode resolution or for widget properties resolution.
=> need to expose:
- field variables like the template widget type does
- xpath like variables to be able to use the current doc path
- widget controls and properties
Also there is a mix between the different ways to expose variables at build time and render time, need to check if this can be cleaned up as the layout system produces a lot of UIAliasHolder tags (and it may produce less, or optimize what's exposed to the context, see for instance fix for NXP-12882)
- depends on
-
NXP-12882 Fix "activate dev mode" ajax refresh on admin center Studio tab
- Resolved
- is required by
-
NXP-14976 Allow using named fields in widgets
- Resolved
-
NXP-10406 Expose property object (and xpath) inside the rendering context in Layout / Widgets
- Resolved
-
NXP-9434 Make it possible to use value bound to field in widget modes expressions
- Resolved
-
NXP-10424 Improve list widget management in lists of lists in edit mode
- Resolved