TRAINING : Creating sub-processes

Adding to above practitioners suggestions, also if you think that the parameters are not mandatory and you don't want to pass the values for these parameters then try defining any one parameter as null() hence all the parameters (8) will be treated as null as mention below:

rule!yourRuleName(
yourFirstParamName: null()
)

Here appian understands that you want want to pass the value for only one parameter and in fact that too is null()

Thank for your help.

After investigating harder, i think that I miss one step I found in the word document (see below) :

 

I don't understand where I can find this windows :-/ 

I found what's wrong. ac! variable is needed instead of pv! value in the first User Input Task. I don't really understand why, if someone can explain it will be nice :)

I found what's wrong. ac! variable is needed instead of pv! value in the first User Input Task. I don't really understand why, if someone can explain it will be nice :)

You use AC! variables for forms. Think of this as a local variable vs a global variable (pv!). Activity class parameters are only available on the node in which they are defined, in this way, you can manipulate the data in the ac without changing the value of the pv! if it is needed in another node in parallel.