I added some global variables. The first task in my process is a human task with no form attached. The second task of the proces is also a human task with a form.
In Pool → Pageflow → Form the Skip option has been selected. When I execute the process by hitting Play I get the “A task is now available” message from the first task, which is fine and when I click on that task I see a form with all the global variables to be set.
How can I avoid that form? Is it a bug?
I’m using Bonita BPM Community Edition v6.3.6 in Linux.
Nope, not an error, that’s the way it works.
To stop this happening - add a pageflow page…
regards
Seán
Thanks for your answer Sean. I have to confess that your answer confused me a little bit 
I understood that Pageflow Skip was meant not to show that initial (debug?) screen with all the variables. Further more, the tooltip of that feature states
If selected, this task will behave like an auto-submit. This means that this require the user to open the step page, that will be auto-submitted. It is not the same as an abstract task.
That is exactly what I’m looking for. However, the tooltip doesn’t mention anything about a form with all global variables being displayed.
- So what is Pageflow Skip for? What impact does it have in a human task that requires no form at all but does require the user to open the step page?
According to your answer it seems whenever I have a human task with no form I will always have to create an empty (just with a submit button) form to accept the task. Doing this for every human task that doesn’t require a form is really a waste of time. Not to mention we are forcing the user to click on the task and then to submit the form, while clicking on the task should be more than enough.
- So can you confirm that creating a form for every single human task, that requires no other user interaction than starting the task, is the Bonita way to represent this tasks?
Thanks in advance.
Uhm, yes I got a little confused by your answer also…then I reread your requirement tested it and then…ah ha.
First, the Pool-Pageflow is being skipped…this can be seen by the
When I execute the process by hitting Play I get the “A task is now available” message from the first task
This ONLY happens after Pool-Pageflow workings is complete.
The form you are seeing is the default Pageflow for the first Human task and Human Tasks BY DEFINITION have pageflows-forms, because a human has to interact with it, because it is a Human Task. There is also NO button to Pageflow-SKIP for a human task. So I think you have the two things mixed up a little.
Yes I was confused a while back by the way the forms worked and once I understood it all works as it should.
What you need to do in this case is reclassify the first task to something else, like a service task or an abstract task. If there is no-human interaction…don’t give it to the human. I mean what is the task doing?
Hope this helps…
regards
Seán
PS - A Summary
POOL → pageflow (show form) or pageflow skip (no form)
then a confirmation…
STEP1 → if Human task ALWAYS show a form (either customized or default (all fields)), can be multiple forms…
on pressing submit → show a confirmation…
STEP2 → if Not Human task then do it with no interaction with the user…
STEPn - any combination of the above two steps…
Human Tasks BY DEFINITION have pageflows-forms, because a human has to interact with it, because it is a Human Task
Makes a lot of sense. That explains everything. I’m using Bonita at College and I was asked to create a human task that was basically something like “Client says hello” (I admit I’m being mean here).
In that case it doesn’t make sense to create a form with a “Submit a hello” button so I thought about just hiding the form but then there is no human interaction, of course. So my options are:
- Make the task abstract
- Remove the unnecessary task
- Create the form with a submit button
Definitely not up to me but, if it was, I would go for #2
Your comments have been very helpful. Thank you very much for time!
It’s a pleasure, good luck,
Seán