Sometimes I use a task (button) to start a process flow. The task in itself actually does nothing, it only calls the process flow. For these kind of tasks I use the tasktype ‘Stored procedure’ and leave the template empty. I noticed that there are other tasktypes available that are not described (like ITP Interface). Could one of these tasktypes be a better option here?
Page 1 / 1
The tasktype 'Stored Procedure' appears to be a fine option for this construction. It's not necessary to link a template to the task.
The ITP Interface is not supported anymore. This used to be a link to the ITP document generation system.
The ITP Interface is not supported anymore. This used to be a link to the ITP document generation system.
In version 2018.2 we added the task type None specifically for this purpose.
Is 'none' the right name for this? I mean, the only purpouse is (I guess) starting a process flow. Why not call it what it is, something like 'Manual process flow execution'?
Edit: Thinking about this, 'none' could also be used to retrieve additional information, where the fields can be filled from the default procedure. This saves space, by not needing a tab or even a complete form on a list of (read-only) information.
Edit: Thinking about this, 'none' could also be used to retrieve additional information, where the fields can be filled from the default procedure. This saves space, by not needing a tab or even a complete form on a list of (read-only) information.
When you compare it to 2018.2, 'None' might seem a bit weird. However, all types have been renamed in 2018.3 to better reflect the type of logic that is used in this task.
This is why it's called 'None'.
This is why it's called 'None'.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.