"david.lloyd(a)jboss.com" wrote : The thing that bothers me is that all the top
level searches would then have a number of fields in common.
|
That is why i would put them on one page. On top you could have a radio button to specify
what you're looking for: process definitions, process instances or tasks.
Then depending on that choice, you could enable/disable certain parts of the form to enter
search criteria.
"david.lloyd(a)jboss.com" wrote : Also, I put Deploy Process Definition at the top
level because there are no other management functions that I know of (you have ... after
it) :-)
|
* (Re)binding process states to specific sub process definitions.
* Checking the size of the logs
* Migrating process instances or process definitions to another db
* Avg tx time
* ...
Currently, there are not many implemented, but this should definitely grow, i think. Keep
in mind that all of these should also be exposed via the JBoss operations network.
"david.lloyd(a)jboss.com" wrote : Also, many of the stats queries depend on
providing a process definition. So I thought it makes more sense, and would be simpler in
any case, to provide these stats queries from a process definition page, where the user
has already located the process definition and they want to find out more about it.
You could have one search page as described above. You might for instance start from that
page and get a list of process definitions. Then for each process definition there might
be a link called 'search process instances'. When clicking that link, you could
navigate to that same search screen with process instances already selected as the items
to search for and also the selected process definition prefilled in the criteria.
Is the idea clear ? I could sketch out something if that helps to get the picture.
What do you think of the idea ?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975487#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...