[Design of JBoss jBPM] - Re: new simplified menu structure
by bazoo
Hi all, great work on the console. A few questions/suggestions from a BA point of view:
General comment is that I think the navigation could be simplified without affecting functionality.
The Process menu shows "No Instance" and "No Definition", when I first start the server, even though I definitely do have a process definition in there.
I don't really understand the point of the Task menu, given that you can navigate to the task through the user task list, which is a more natural way to get to the screen.
I would suggest that "Start new instance" should be more easy to find. It takes a bit of hunting around before you can work out how to start a new instance. If anything it should be a sub-menu item underneath Process.
Responding to Jeff's suggestion, I would suggest that "acquire" has a slightly different meaning to "take". Semantics I know, but what is wrong with "Take" anyway?
I would not incorporate the "Search for instance" row in the task list, at least not at the top. For someone new to the app, you don't immediately notice that you have a task in the task list because it is hidden in small text underneath the big search boxes. You immediately think you have to perform a search, even though you may not have to.
Why doesn't the Task Instance and Definition view become active until I have "Viewed" the task in the User Task List? Surely it should become active as soon as there is a task.
Why can any old user re-assign a task? I would have thought that given we have assigned a task to a particular swimlane in the process definition then that swimlane should do the task, unless there is some exceptional reason. I would have thought this functionality should be restricted to "managers". Otherwise people will not do any work and will just re-assign tasks to other people all the time!
I don't understand what the "Task Definition View" is really.
I don't think the Summary page should be the first page you see when you click Task Instance View. I think it should be the Task Form to minimize clicking.
Instead of "End Task", I would suggest "Proceed", to reinforce the idea that the user is moving through a process.
I get the following exception when I click "End task" or "More info needed", although the transition does happen: javax.el.PropertyNotFoundException: /main/task/new_tasks.xhtml @41,57 value="#{entry.taskInstance.id}": Property 'taskInstance' is not found on type: java.lang.String
I would suggest that "User Task List" should be at the top of the navigation menu, especially as it is the view you go to first when you log in.
When you start a new instance of a process, the console has a "show details" link. If I click it it just comes back telling me the task instance ID. I don't think that's really worth hiding!
Cheers
Matt
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998496#3998496
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3998496
19 years, 3 months
[Design of AOP on JBoss (Aspects/JBoss)] - AOP Tests
by kabir.khan＠jboss.com
I've got most of the tests passing again with jdk 5 now, apart from the following two.
1) org.jboss.test.aop.bridgemethodnotwoven.BridgeMethodTestCase(jdk50)
This is due to a fix that was put into JavassistMethodHashing, which in turn broke the MethodHashingTestCase (which was disabled for a while, waiting for a release of MC). I've fixed JavassistMethodHashing so that MethodHashingTestCase, which is the acid test runs again. BridgeMethodTestCase needs to be looked at again though.
The other failing test on jdk 5 is
2)org.jboss.test.aop.regression.jbaop248annotationoverride.AnnotationOverrideTestCase(javaagent-genadvisor-tests), which passes in all the other modes it is run.
Most of the failures were fixed using privileged blocks, it seems that later updates of JDK 5 are more strict when it comes to security?!
We need to look at the JDK 1.4 tests as well, for them to pass we need a retroed version of the mc/container project, and iirc there were some problems with that due to some new features in the codebase not supported in jboss retro :-(
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998435#3998435
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3998435
19 years, 3 months
[Design of JBoss jBPM] - Re: direct navigation when starting a new process instance
by jeffdelong
This is a bit tricky, because these are really two different scenarios here.
1) if Start-task - then user should be navigated to the page to perform the task, i.e. fill in the form.
2) no Start-task - typically the user that started the process will not perform the first task in the process (otherwise we could have modelled their task at the start). So they should not navigate to a task-related page. Question is where to take them. What they would probably most like to see is the list of started processInstances, and see the one they just started in that list, or the ProcessInstance View for that particular instance that they just started.
By the way, with the websale process I get an exception from the TaskInstance page when i hit the End task button:
javax.el.PropertyNotFoundException: /main/task/new_tasks.xhtml @41,57 value="#{entry.taskInstance.id}": Property 'taskInstance' is not found on type: java.lang.String
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998393#3998393
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3998393
19 years, 3 months