7 Replies Latest reply: Aug 2, 2011 2:48 PM by Zeeshan BaiG RSS

    No task flow return activities are defined

    734873
      Hello,

      I am using JDev 11.1.1.4.0.

      I have a bounded task flow as below. It runs fine, but there is one error and one warning that makes me nervious.

      Error> No task flow return activities are defined
      Warning> No data control scope is defined

      Is it ok to ignore them?

      Thanks,

      Bones Jones
      <?xml version="1.0" encoding="windows-1252" ?>
      <adfc-config xmlns="http://xmlns.oracle.com/adf/controller" version="1.2">
        <task-flow-definition id="myPageFlowDef">
          <default-activity id="__1">myPage</default-activity>
          <view id="myPage">
            <page>/ui/pages/myPage.jspx</page>
          </view>
          <view id="secondPage">
            <page>/ui/pages/secondPage.jspx</page>
          </view>
          <method-call id="setCurrentmyPagesecondPageRowWithsecondPageId">
            <method>#{bindings.setCurrentmyPagesecondPageRowWithsecondPageId.execute}</method>
            <outcome id="__29">
              <fixed-outcome>setCurrentmyPagesecondPageRowWithsecondPageId</fixed-outcome>
            </outcome>
          </method-call>
          <control-flow-rule id="__13">
            <from-activity-id id="__14">secondPage</from-activity-id>
            <control-flow-case id="__16">
              <from-outcome id="__17">gotomyPage</from-outcome>
              <to-activity-id id="__15">myPage</to-activity-id>
            </control-flow-case>
          </control-flow-rule>
          <control-flow-rule id="__30">
            <from-activity-id id="__31">myPage</from-activity-id>
            <control-flow-case id="__32">
              <from-outcome id="__34">setKey</from-outcome>
              <to-activity-id id="__33">setCurrentmyPagesecondPageRowWithsecondPageId</to-activity-id>
            </control-flow-case>
          </control-flow-rule>
          <control-flow-rule id="__35">
            <from-activity-id id="__36">setCurrentmyPagesecondPageRowWithsecondPageId</from-activity-id>
            <control-flow-case id="__37">
              <to-activity-id id="__39">secondPage</to-activity-id>
            </control-flow-case>
          </control-flow-rule>
        </task-flow-definition>
      </adfc-config>
        • 1. Re: No task flow return activities are defined
          Zeeshan BaiG
          Bounded task flows must use return activity.

          1. Simple drag and drop the Return activity from Component palette
          2. select the task flow and set the property of Data control scope to Shared or isolated..

          also check this video i guess i explained a task flow outcome a bit
          http://baigsorcl.blogspot.com/2011/07/how-to-execute-java-code-before-and.html

          Zeeshan
          • 2. Re: No task flow return activities are defined
            Timo Hahn
            @Zeeshan The 'Fusion Developer's Guide' 14.1.2 Task Flow Types (http://download.oracle.com/docs/cd/E23549_01/web.1111/b31974/taskflows.htm#BABDJEDD) states that you don't need an exit point. So I don't see why to define a return activity
            Bounded task flow: A specialized form of task flow that, in contrast to an
            unbounded task flow, has a single entry point and zero or more exit points.>

            The data control scope defines how a task flow handles data, e.g. if the task flow creates a new data control instance (isolated) or if it uses the parent one (shared) which is the default. So you can ignore the warning.

            Timo
            • 3. Re: No task flow return activities are defined
              734873
              So, what I am getting is that:

              1. I can just drag and drop 'Task Flow Return' activity to my task flow page and do nothing with it.
              2. The warning about scope can be ignored.

              Please let me know.

              Thanks,

              Bones Jones
              • 4. Re: No task flow return activities are defined
                Navaneetha Krishnan Nataraj
                Hi Bones Jones,

                Can you provide full logs for this error:
                Error> No task flow return activities are defined
                As mentioned by Timo, we need not have any exit points (return activities) in a task flow.
                Check if added a return activity solves your issue? But i am still surprised why we need this?

                Thanks,
                Navaneeth
                • 5. Re: No task flow return activities are defined
                  Timo Hahn
                  1.) yes
                  2.) You can set the scope, check http://download.oracle.com/docs/cd/E12839_01/web.1111/b31974/taskflows_parameters.htm#insertedID4
                  The warning should go away if you set the scope to shared. If you like it to be isoloated set it to shared, safe the work and unset the check box again.

                  Timo
                  • 6. Re: No task flow return activities are defined
                    734873
                    Navaneetha,

                    The error only appears in xxxDef.xml - Structure window. Also it is visible when looking at the xxxDef.xml source on the task-flow-definition tag. At run time, I have not had any problem with this error.

                    Yes, just dropping the activity made the error go away. I didn't do anything else other than dropping it.

                    Thanks,

                    Bones Jones
                    • 7. Re: No task flow return activities are defined
                      Zeeshan BaiG
                      Timo Hahn wrote:
                      @Zeeshan The 'Fusion Developer's Guide' 14.1.2 Task Flow Types (http://download.oracle.com/docs/cd/E23549_01/web.1111/b31974/taskflows.htm#BABDJEDD) states that you don't need an exit point. So I don't see why to define a return activity
                      Bounded task flow: A specialized form of task flow that, in contrast to an
                      unbounded task flow, has a single entry point and zero or more exit points.>

                      The data control scope defines how a task flow handles data, e.g. if the task flow creates a new data control instance (isolated) or if it uses the parent one (shared) which is the default. So you can ignore the warning.

                      Timo
                      Thanks Timo for the link. i agree with you but if you have a bounded task flow initiates the transaction then you are required a exit point else the task flow gives you warning. i personally likes to get rid of the warnings as well.

                      Zeeshan