Do not attempt to use the template as though it was code. A template is a model display definition and if you put logic in it, you are breaking the MVC Separation of Concerns contract, and that, in turn, makes your application much harder/more expensive to maintain. The only logic on a JSF template should be stuff that directs the rendering of the template elements.
JSF isn't designed with the idea of passing arbitrary data to and from the client. Except for form data, JSF normally expects all data to be residing on the server (in backing beans, or at least accessible via backing beans). So there's no need to code references to the application data in constructs like parameters on the View Template.
JSF EL supports doing stuff like that, but that's because no one solution fits everything. There is a cost involved, however, which is why doing stuff like parameters on templates should be the last resort of a knowledgeable developer, instead of the first resort of someone who just wants JSF to work like more primitive systems do. The whole point of using JSF instead of more primitive solutions is precisely because the primitive systems require more work to get things done.
Customer surveys are for companies who didn't pay proper attention to begin with.
subject: Passing both action method names and parameters as arguments to facelets componenets