[BUG] Page composer does not pass task flow input paramters correctly

Question

Hello,
When using the page composer to add a task flow requiring parameter to an editable region, the pageDef is correctly created within the MDS store. In my test case, the generated pageDef looks like the following, which seems to be correct:
<?xml version = '1.0' encoding = 'UTF-8'?>
<mds:customization version="11.0.0.49.49" xmlns:mds="http://xmlns.oracle.com/mds">
   <mds:insert parent="pages_test_testWebCenterComposer2PageDef(xmlns(mds_ns1=http://xmlns.oracle.com/adfm/uimodel))/mds_ns1:executables">
      <taskFlow id="regionBinding1" taskFlowId="/taskflows/texte-riche-task-flow#texte-riche-task-flow" xmlns="http://xmlns.oracle.com/adf/controller/binding" Refresh="ifNeeded"/>
   </mds:insert>
   <mds:insert parent="pages_test_testWebCenterComposer2PageDef(xmlns(mds_ns2=http://xmlns.oracle.com/adf/controller/binding)xmlns(mds_ns1=http://xmlns.oracle.com/adfm/uimodel))/mds_ns1:executables/mds_ns2:taskFlow[2]">
      <parameters xmlns="http://xmlns.oracle.com/adf/controller/binding"/>
   </mds:insert>
   <mds:insert parent="pages_test_testWebCenterComposer2PageDef(xmlns(mds_ns2=http://xmlns.oracle.com/adf/controller/binding)xmlns(mds_ns1=http://xmlns.oracle.com/adfm/uimodel))/mds_ns1:executables/mds_ns2:taskFlow[2]/mds_ns2:parameters">
      <parameter id="idStellent" xmlns="http://xmlns.oracle.com/adfm/uimodel"/>
   </mds:insert>
   <mds:insert after="pages_test_testWebCenterComposer2PageDef(xmlns(mds_ns2=http://xmlns.oracle.com/adf/controller/binding)xmlns(mds_ns1=http://xmlns.oracle.com/adfm/uimodel))/mds_ns1:executables/mds_ns2:taskFlow[2]/mds_ns2:parameters/mds_ns1:parameter">
      <parameter id="mode" value="edit" xmlns="http://xmlns.oracle.com/adfm/uimodel"/>
   </mds:insert>
</mds:customization>Since it was not working as I expected, I added a method call printing the parameters values as the first action of my task flow, but I get the following, showing that none of the parameters ever get passed to the task flow. Of course, in its current state idStellent should indeed be null, but the mode should have the static value "edit":
------------------------ idStellent = null, mode = null ------------------------Can we get a ticket filled for this issue because it's an extreme blocker for us as it prevent reuse of task flows with the page service.
Regards,
~ Simon

Answer 1

Hi,
I forgot to mention that the task flow is extremely simple, here's its definition:
<?xml version="1.0" encoding="windows-1252" ?>
<adfc-config xmlns="http://xmlns.oracle.com/adf/controller" version="1.2">
  <task-flow-definition id="texte-riche-task-flow">
    <default-activity>printParams</default-activity>
    <input-parameter-definition>
      <name>idStellent</name>
      <value>#{pageFlowScope.idStellent}</value>
      <class>java.lang.String</class>
    </input-parameter-definition>
    <input-parameter-definition>
      <name>mode</name>
      <value>#{pageFlowScope.mode}</value>
      <class>java.lang.String</class>
    </input-parameter-definition>
    <managed-bean>
      <managed-bean-name>document</managed-bean-name>
      <managed-bean-class>ca.ulaval.ena.faces.bean.HtmlStellentDocumentBean</managed-bean-class>
      <managed-bean-scope>pageFlow</managed-bean-scope>
      <managed-property>
        <property-name>idStellent</property-name>
        <property-class>java.lang.String</property-class>
        <value>#{pageFlowScope.idStellent}</value>
      </managed-property>
    </managed-bean>
    <managed-bean>
      <managed-bean-name>block</managed-bean-name>
      <managed-bean-class>ca.ulaval.ena.webcenter.bean.BlockBean</managed-bean-class>
      <managed-bean-scope>request</managed-bean-scope>
    </managed-bean>
    <view id="texteRiche">
      <page>/fragments/ut412/texteRiche.jsff</page>
    </view>
    <view id="texteRicheEditable">
      <page>/fragments/ut412/texteRicheEditable.jsff</page>
    </view>
    <router id="modeSwitch">
      <case>
        <expression>#{pageFlowScope.mode == 'edit'}</expression>
        <outcome>edit</outcome>
      </case>
      <default-outcome>read-only</default-outcome>
    </router>
    <method-call id="printParams">
      <method>#{block.print}</method>
      <parameter>
        <class>java.lang.String</class>
        <value>#{pageFlowScope.idStellent}</value>
      </parameter>
      <parameter>
        <class>java.lang.String</class>
        <value>#{pageFlowScope.mode}</value>
      </parameter>
      <outcome>
        <fixed-outcome>done</fixed-outcome>
      </outcome>
    </method-call>
    <control-flow-rule>
      <from-activity-id>texteRicheEditable</from-activity-id>
      <control-flow-case>
        <from-outcome>annuler</from-outcome>
        <to-activity-id>texteRiche</to-activity-id>
      </control-flow-case>
      <control-flow-case>
        <from-outcome>ok</from-outcome>
        <to-activity-id>texteRiche</to-activity-id>
      </control-flow-case>
      <control-flow-case>
        <from-outcome>enregistrer</from-outcome>
        <to-activity-id>texteRicheEditable</to-activity-id>
      </control-flow-case>
    </control-flow-rule>
    <control-flow-rule>
      <from-activity-id>modeSwitch</from-activity-id>
      <control-flow-case>
        <from-outcome>read-only</from-outcome>
        <to-activity-id>texteRiche</to-activity-id>
      </control-flow-case>
      <control-flow-case>
        <from-outcome>edit</from-outcome>
        <to-activity-id>texteRicheEditable</to-activity-id>
      </control-flow-case>
    </control-flow-rule>
    <control-flow-rule>
      <from-activity-id>printParams</from-activity-id>
      <control-flow-case>
        <from-outcome>done</from-outcome>
        <to-activity-id>modeSwitch</to-activity-id>
      </control-flow-case>
    </control-flow-rule>
    <use-page-fragments/>
  </task-flow-definition>
</adfc-config>Note that the method call at the start is totally useless and only used to print the input parameters.
~ Simon