View State

[julian_k]

As I think about jBPM and Task Controllers, I wonder what is the best way to associate a view with a given state in the workflow engine. In jbpm one, I had a mapping file associated with each state in the wokflow engine for holding metadata related to the view. The current webapp example simply uses text boxes for each form parameter. Although this works, it makes for pretty basic forms. So I ask, are there current documented plans on how to improve the UI mapping to workflow states? If not, what are the current leading thoughts for showing a form for a given task?

Thanks,
Julian

[julian_k]

I am still trying to achieve a mapping b/w a given task and a view. Currently, I am integrating with a pre-existing web application...and would like to show one of the pre-existing webpages when a user clicks on the title of the TaskInstance in their inbox. Has their been any discussion on how to achieve this?

Thanks,
Julian

[kukeltje]

I am working on this in my spare time. Currently I can
- have a default tasklist page which is accessed if no special pages are configured
- have each transition from the tasklist go to a specific page. This is done by having the 'state name' as an action in the faces-config.xml
- have each transition from this specific page go to another specific page based on the transition names
- have fully customizable jsp pages with own positioning of variables and use their specific type.

Wait for more in a few days

[julian_k]

The problem I see with your approach of mapping state names to a URL in your faces-config is that going to a view doesn't always mean leaving the current state of the process instance. Also, with this in place you cannot have a task assigned to a given view b/c the task would be lost once the user follows the transition. I am still thinking this one through, but thats just my two cents.

Julian