Different releases support different browser versions.  Which version of the product are you interested in knowing about?  Can we assume version 11.2?Author: Keith SwensonAttachment:

There actually is no reason to accept the task before completing it, since the task is "automatically" accepted at the time that you complete it.The question would be: why would ANYONE want to force the user to take two steps to do something, when they could easily do it in one?   This is completely backward from a usability perspective.  What does the person who is requesting this think they are going to gain with requiring people to take an extra step?  Do they think they get extra security?  (they don't)  Do they think that this will inform others about what the use is doing? (it doesn't)  Do they think that this will prevent users from accidentally stepping on each other? (it doesn't)  Do they think it annoys people and keeps them from doing too much work?  (yes, this it does)When discussion workflow design, I often encounter people asking for this, but it is usually on the misguided idea that one can force the user to accept the task *early on, before they start doing the work.*   This would inform others that the task is being worked on, and prevent duplicate work.  However, this has nothing to do with "completing the task".  What instead is needed is a way to display part of the task information ONLY if the task is accepted.  I don't know if this can be done with the forms, but customers has implemented this sort of thing with their UI.You will find that there is a broad spectrum of tasks to consider.  Some are long term tasks that should be accepted hours or days before completing.  But there are also many others that can be completed in a few seconds ... sometimes faster than the page refresh.  In many cases, a person will receive a task for something they have already completed.  In this case, they recognize the case, and take the action.  Forcing them to accept the task in these cases is simply a bother, and adds no value.If you are consider this capability, please consider more and carefully think through all the use cases, because we found that most people who initially used this, ended up turning it off because it was not really what they wanted.Author: Keith SwensonAttachment:

This is where the border between an application and the system becomes fuzzy.Most production applications have some custom user interface for the production users to use.  The Interstage BPM Console is really oriented toward process managers / business analysts than toward end users.  The Console allows a process manager to experiment with queries, and do ad-hoc investigations.An application with a custom UI certainly can have a default worklist for all users, and that is what I would recommend.  It is not likely that you are going to want to use the Console for production work, but a JSP could be added to an application to provide a common worklist for all users (of that application) within the console.I can see possibly wanting a default worklist for all the Console users, but that is not a feature of the Console at this time.Author: Keith SwensonAttachment:

The real answer is a little more complicated.  When you design a process, you can attach to any activity any kind of form.  The definition of "form" is not constrained -- it is really just a string that has meaning to the client.  The Interstage IBPM Console is one such client, and it understands quick forms and JSP forms.Many of our customers have a custom client which uses the model API to access workitems and process instances for the production users.  Such a custom client can use JSF forms if desired.  The client would include the additional classes that would read and render the forms.Finally, there is a possibility that JSF forms would work in the Interstage BPM Console, and that is if you add the JSF support classes to the application (as libraries) and then you can make JSP files which read and render the JSF forms.  I don't know how hard this would be to integrate (not knowing JSF forms) and sometimes such frameworks have constraints/assumptions that prevent one framework from working inside another.  Some further research would be needed to find out whether JSF forms would work inside the Interstage BPM console.But a custom web application that reads worklists and displays task information using JSF is certainly possible.Author: Keith SwensonAttachment:

Yes, we have published APIs for Dynamic Interstage BPM.The best place to look for the answer to such a question is the Developer’s Guide, which describes the capabilities of the product from a programming perspective.For the Dynamic Interstage BPM apis look at the sectionsUsing Dynamic SubtasksUsing Dynamic Processes Author: Keith SwensonAttachment: