When using custom variables in the action context resolution, it would be useful to be able to use the same variables in the action definition (link, properties).
This can be done by taking action context variables and exposing them in the rendering context (for now, variables are only available to filter conditions resolution context).
This should help extracting actions for the file widget (
This should also allow defining more generic actions in content view selections: since the selected elements, as well as selection list name, are available in this context, they can be referenced by actions, and corresponding seam components can stop hardcoding retrieval of these elements. This will help redefining selection actions for custom content views.