How to disable buttons in ADF form so it can be reused

Question

I would like to reuse the same Human Task ADF form for multiple User Activities in the same BPM 11g process definition.  The only difference between the User Activities in the process are the outcomes (buttons) allowed.  For example, in some User Activities, the outcomes allowed are APPROVE and REJECT.  In others, it might be APPROVE, REJECT, and REPROCESS.  Is it possible to hide, or disable, buttons in a Human Task ADF form based on some settings done in the User Activity, or something passed to the Human Task ADF form?
I started digging, and I see in the jspx file for the form, there is an attribute named "visible" that is set as follows on the button:
<af:commandToolbarButton actionListener="#{invokeActionBean.setOperation}"
                       text="#{wf:getResourceValue('APPROVE', 'bindings.customActions')}"
                       disabled="#{!bindings.APPROVE.enabled}"
                       action="#{invokeActionBean.invokeOperation}"
                       partialSubmit="false"
                       visible="#{wf:isCustomActionAvailable('APPROVE', 'bindings.customActions')}"
                       id="ctb2">
    <f:attribute name="DC_OPERATION_BINDING" value="bindings.APPROVE"/>
</af:commandToolbarButton>
So if I can figure out a way to pass flags to the form, and then use those in the setting of the "visible" flag, would that do it?  Is there a better method?
Thanks,
Joe A.

Answer 1

Set the binding to the button in the managed bean based on the input form parameter. For example if parameter value is paramValue1
<task-flow-definition id="sourceTaskflow">
  <input-parameter-definition>
      <name>inputParameter1</name>
      <value>#{pageFlowScope.paramValue1}</value>
      <class>java.lang.String</class>
   </input-parameter-definition>
</task-flow-definition>
Set binding to not enabled.
#{!bindings.CreateInsert.enabled}
Some relevant references
http://www.oracle.com/technetwork/developer-tools/adf/learnmore/oct2010-otn-harvest-183714.pdf
Using Parameters in Task Flows