Hello Pedro,

The documentation pages that you mention are about two special actions (Process Extended Actions) that allow you to close Human Activities and Wait Activities. They are specific to each Human or Wait Activity and because of this they are called Close<Human Activity Name> or Close<Wait Activity Name>.

These actions have input parameters, but they are all automatically defined by the platform.

The first one is the Activity ID, which allows you to identify the Human Activity or Wait Activity that you are going to close.

The other input parameters correspond to the output parameters of their corresponding Human or Wait Activity. So, if you define a Human Activity with two Output Parameters Out1 and Out2, the Close Action will have two input parameters with the same name and type:

When you call the Close action, you need to the define the value of these input parameters in the Properties pane.  This is the mechanism that allows you to define the outcome of the activities when you close them:

So, indeed, the documentation can be a bit confusing if you only read about the Close Actions without having read about the Activities and how this mechanism works. We thank you for your feedback and will take it into account when we improve this area of the documentation.

Do let us know if this makes more sense now or if you still have any questions!

Hi Paulo and Ângela, thanks for your messages. 

@Paulo: your explanation is "crystal clear". To clarify matters in the documentation, I would suggest the following:

1) Rephrase the explanation in the documentation. Instead of having "Human Activity Input Parameters: one parameter for each input parameter in the human activity definition.", write down the following "Human Activity Output Parameters: one parameter for each output parameter in the human activity definition."

2) Under this statement, you could add the example presented in here by Paulo.

Thanks again for the time taken clarifying this issue.

Greetings, Pedro