I'm not quite sure what you mean, so some further examples might help. It might be that you want to have the action create different incident processes and that be able to have different forms for these. That you can do, but you'd need to do some process work. Indead of just using the action directly, you create an action of your own to collect the data and then use an automatic action in the process to create the child. The key is that in process designer you can change the default process used to be one that you want. That then launches the right process wit hthe right form.
You can do the same trick with tasks too.
I agree with Dave, can you provide some more information about what you're trying to achieve. There are methods of enabling the creation of different processes within a workflow and what Dave has described is the most common, but it might not be the right approach in the first place.
Please refer to my attachment.
The picture was created by mspaint (not real in the LANDesk), but can be describe the condition that I want to achive currently.
Is that possible or not?
Untitled.jpg 30.8 K
Yes. You will need to write 6 custom actions in the process each with the right name to collect the data on 6 different forms for 6 different processes. Then use process designer to fire off an automatic action(s) at the right point to create a child incident with the right process name in the action instance details. Depending on what these processes are designed to do, I'd seriously consider using the same trick to generate tasks as an alternative approach.
But if you need to have full incidents and not tasks, then it will work fine.
I'd suggest you make sure you have enough process licenses left before starting along this route. This will not matter if you use tasks, but top level processes like incidents are counted by the product and you will not be able to activate more than you are licnesed for.