Is there a way to avoid activity chaining?

Certified Associate Developer

Hello,

I created an application where the number of nodes existing between 2 user interface form has more than 50 activity chaining associated, Due to which its getting break and the user is not able to see the second form instead from their Task tab. I know it should not exceed more than 50 but i don't have any control over it as it include couple of subprocesse as well. Is there a way to get rid of this problem? Thanks in advance

  Discussion posts and replies are publicly visible

Parents
  • Hi Vivek -

    The first thing to look at is, for process flow sequences in which two or more script tasks follow in succession, did the designer use both the inputs and outputs tabs in each of those script tasks?
    Often, a designer will create a script task to calculate or query "predicate" data for use in a dependent expression in a 2nd script task. This is sometimes very easy for designers to "wrap their heads around." However, it's not always the most efficient design.
    Instead of passing data from one node to another in a PV, pass data from the inputs tab to the outputs tab using an ACP.
    Also, you can run several expressions on inputs and outputs.
    Remember, when you're tuning, that the inputs tab always evaluates before the outputs tab, but, there's no guaranteed order of expression evaluation within each tab.

    Next, review the operations that are taking place in these nodes and consider how many you could logically calculate in your SAIL forms. It's possible that you can inexpensively calculate some expressions using the saveInto on the submit of the first form, and/or the load of the 2nd form.
Reply
  • Hi Vivek -

    The first thing to look at is, for process flow sequences in which two or more script tasks follow in succession, did the designer use both the inputs and outputs tabs in each of those script tasks?
    Often, a designer will create a script task to calculate or query "predicate" data for use in a dependent expression in a 2nd script task. This is sometimes very easy for designers to "wrap their heads around." However, it's not always the most efficient design.
    Instead of passing data from one node to another in a PV, pass data from the inputs tab to the outputs tab using an ACP.
    Also, you can run several expressions on inputs and outputs.
    Remember, when you're tuning, that the inputs tab always evaluates before the outputs tab, but, there's no guaranteed order of expression evaluation within each tab.

    Next, review the operations that are taking place in these nodes and consider how many you could logically calculate in your SAIL forms. It's possible that you can inexpensively calculate some expressions using the saveInto on the submit of the first form, and/or the load of the 2nd form.
Children
No Data