Unwanted starting of taskflows

Question

Hi, I have unbelievable problem with taskflows.
I am using JD Studio Edition Version 11.1.1.5.0 on Weblogic 11.1.1.5
I have page with 4 popups (new, assign, assume, return). Each popup has dialog and region with taskflow. Popup and region are binded in backing bean.
Popups are showed by buttons on page. Button action call methodCall like this:
    public void showNewBook() {
        setNewBookPopupVisible(true); //enable to start taskflow because taskflowregion has activation=conditional and active gets this value
        getNewBookRecordRegion().refresh(FacesContext.getCurrentInstance()); //activate region
        AdfFacesContext.getCurrentInstance().addPartialTarget(getNewBookRecordRegion());
        getNewBookRecordPopup().show(new RichPopup.PopupHints()); //activate popup
        AdfFacesContext.getCurrentInstance().addPartialTarget(getNewBookRecordPopup());
When I push button "Assume" I see in the log
<workOnBook> <assumeBook> entering
<LoggingWrapper> <initLogger> Logger initialized. Identifier = task-flow-content-books-popup-assume
<LoggingWrapper> <initLogger> Logger initialized. Identifier = task-flow-content-books-popup-assume
<LoggingWrapper> <initLogger> Logger initialized. Identifier = task-flow-content-books-popup-assign
<LoggingWrapper> <logInfo> <task-flow-content-books-popup-assign> log: BOOKID=[6] SelectedRow n0 =[2170769]
<workOnBook> <prepairFormForAssign> Called.
<workOnBook> <prepairFormForAssign> BookRecordId: 2170784
<workOnBook> <prepairFormForAssign> BookId: 74
<workOnBook> <prepairFormForAssign> state: 20
Assign popup is not shown but it works on background. task-flow-content-books-popup-assign does createInsert and I can see it in parent window after close of Assume popup.
Thank you for help.

Answer 1

There is nothing strange. Taskflow bindings of the regions are in the executable section of the parent page, so they are executed by default during the PrepareModel phase of the containing page (even if the corresponding regions are not going to be rendered). The corresponding "child" taskflows are created and all their activities up to the 1st view activity are executed (including the CreateInsert activities at the start of the taskflows). You can prevent automatic execution of these taskflows by specifying conditional activation of the taskflows. Use the "activation" and "active" properties of the taskflow bindings for this purpose. Look at the documentation for more details:
Using Task Flows as Regions - 11g Release 1 (11.1.1.5.0)
Dimitar