A short comment from me as well. The wiki page looks already promising. For me, most important would be some easy things: - see the current activity of a process instance (would be sufficient as a column in the table) - See all process instances (not selecting a process definition) By the way: How do I see Child Executions / the Execution Hierarchie? This would be important as well. And and some feedback on the usability: To have the ProcessDefinition/ProcessInstance Tab was a bit confusing for me first. I didn't recognize they have a relationship to each other... Heiko wrote : | Process variable inspection is one of those cases. There is currently no constraint on variables whatsoever. The "hashmap" style of design allows for everything and nothing at the same time. Of course it would be useful have that feature in the console, but without any type descriptions associated with the process it will only work in particular situations and break in others. | I agree with the others, a simple table with the toString representation would be already a big step ahead. With some improvement it may get a generic Tree (e.g. to show lists, maps and object properties easily). This is what we have in a couple of rich clients at some customers already. If you then cann delete, change or add variables/entries (add by specifying the class name), it would be already very sophisticated :-) But this has not a very high priority (even if I had the demand already a couple of times). But I am eager to the see the next evolution of it :-) Heiko wrote : | Currently the console has to cope with a lot of unknowns, which derive from the "everything possible, but nothing mandatory" style of coding that jbpm4 reflects. | Yeah, I think thats the destiny of a generic process engine console ;-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238246#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...