hi, i want to use a sub-process startForm as a user task. went

Why not just add a user input task at the beginning of the sub-process?

hi, because the user can't by-pass the process by a related action. if i do that the user iniate a process when he click on the related action button instead when he submits the form. it's not a "BIG" problem besause most of the time the user submits the form... but i don't understand the aim of having "Form" tab on sub-process smart node

@victorb, may I know what exactly is your requirement ?

As philb mentioned in above comment, you can use a form at the start of sub-process. If your requirement is such that a user has sequence of tasks associated then you can configure chaining.

What do you mean by "the user can't by-pass the process by a related action"?

Instead of using activity class parameters, you will want to map your process variables directly to your SAIL start form. If the process variable is set to be a process parameter, then the SAIL start form will save into that variable. You can find more information on this in the documentation, under "Saving Form Values".
forum.appian.com/.../Process_Start_Form.html

@lakshmim, i agree but i don't want map startForm variables in a process. i want map process input variables on a sub-process smart node (setup tab) to the sail definition on Forms tab.
we have a lot of processes with startForm and i want to use them into a process (as sub-process) whitout modify them. I saw a from tab on the sub-process smart node, but i don't understant the way to map input process variables on sail definition on form tab.

@victorb I'm still not sure why you need to do this. I believe the simple answer is that you can't - but why would you want to? You can just add a user input task inside the sub-process, or one in front of that process.

I've never used the forms tab on a sub-process node, normally the sub-process would be unattended (run as process designer) rather than being an attended node. If it's not an attended node then the forms tab is no longer available.
It sounds like you're trying to prevent the sub-process from running until the user submits this form, so using a start form in the sub-process should give you that same functionality. Or as Phil suggested, you could put the form in front of the sub-process node and add logic to not enter the sub-process if it's not necessary.

thank you for your answers.
i agree with you, there is many solutions, and i'm probably going to put a user task at the beginning of each sub-process. My point was about the specific use of the sub-process Form tab which appears when you assign the sub-process (assignment tab). This functionality was working whit portal forms and i just want to know if is it possible use it with tempo (the sail form acutally appears, but there no way to map input user to the sub-process input variable).

Hi everyone,

We are also facing the same issue unfortunately. The main reason why you want the start form to be on the sub-process but not outside is so that automated activities (document generation, email sender, etc.) are from the user that did the start form. Currently this is an issue for us, as the process is not initiated with the correct user. Does anyone have any other workaround on this?

Thanks,
Krassimir