6 Replies Latest reply on Jan 18, 2007 4:13 PM by falazar

    remove context sensitive menus

    Tom Baeyens Master

      this topic is part of the web console feedback: http://wiki.jboss.org/wiki/Wiki.jsp?page=JbpmConsoleFeedback

      I think it's better to remove the left-hand side context sensitive menus for task instance and process instance.

      These navigations should be offered in the content of the page displayed. See other web console feedback for more info.

      That prevents unavailable links in the menu (or a jumping menu if you would make them dissappear if they are unavailable)

        • 1. Re: remove context sensitive menus
          Jeff DeLong Master

          I agree with Tom. I had problems understanding the left-hand side context menus:

          No Task Available

          No Process Available

          In particular, a submenu says No Definitions, yet I know I have process definitions deployed.

          I also have a comment on Terminology. We seem to be equating Processes with ProcessDefinitions. This is okay, most users don't like to say processdefinitions, but we must always be clear when dealing with instances that we say ProcessInstances, so that the difference is clear.

          • 2. Re: remove context sensitive menus
            Tom Baeyens Master

             

            "jeffdelong" wrote:
            I also have a comment on Terminology. We seem to be equating Processes with ProcessDefinitions. This is okay, most users don't like to say processdefinitions, but we must always be clear when dealing with instances that we say ProcessInstances, so that the difference is clear.


            in the new core prototype, i use the following terminology

            ProcessDefinition --> Process
            ProcessInstance and Token --> Execution

            Maybe that could already be adopted into the web console for 3.2. But probably that would cause more confusion then it solves, no ?

            • 3. Re: remove context sensitive menus
              David Lloyd Master

               

              "tom.baeyens@jboss.com" wrote:
              ProcessDefinition --> Process
              ProcessInstance and Token --> Execution

              Maybe that could already be adopted into the web console for 3.2. But probably that would cause more confusion then it solves, no ?


              I like the new terminology a lot better, but I think that changing to "Execution" now would just be confusing. Changing "Process Definition" to "Process" is perfectly reasonable though, in my opinion.

              • 4. Re: remove context sensitive menus
                David Lloyd Master

                The action here is: Context menus are toast. I'm not going to change to "Execution" for 3.x. But I think that we should work to make "Execution" be the standard term for a process instance+token in 4.x. "Process" will refer to the definition, and "Process Instance" will refer to the instance (for now). Task definitions and instances will continue to be referred to as "Task Definitions" and "Tasks", respectively.

                • 5. Re: remove context sensitive menus
                  Tom Baeyens Master

                   

                  "david.lloyd@jboss.com" wrote:
                  The action here is: Context menus are toast. I'm not going to change to "Execution" for 3.x. But I think that we should work to make "Execution" be the standard term for a process instance+token in 4.x.


                  good conclusion


                  "david.lloyd@jboss.com" wrote:

                  "Process" will refer to the definition, and "Process Instance" will refer to the instance (for now). Task definitions and instances will continue to be referred to as "Task Definitions" and "Tasks", respectively.


                  I don't think that task definitions need to be referred to in the web console. Or do you see a reason that i'm overlooking ?

                  Using the name "Task" for TaskInstance's is good, i think. (as long as there is no reference to a task definition somewhere, which i don't think is necessary)

                  But taking into account all the feedback and consistency, i would keep the complete names of "Process Definition" and "Process Instance".

                  • 6. Re: remove context sensitive menus
                    Novice

                     


                    Using the name "Task" for TaskInstance's is good, i think. (as long as there is no reference to a task definition somewhere, which i don't think is necessary)

                    But taking into account all the feedback and consistency, i would keep the complete names of "Process Definition" and "Process Instance".


                    Correct, keep Process Instance or Process for this, that is the simplest short definition,
                    and matches the Task Instance, Tasks, Task Definition style.

                    Execution is really more of an action term, and not appropriate.

                    Under the Process Definition page, it is not intuitive that all of the stuff is there,
                    "Start" should be moved to another area, and the Process List on the end seems to warrant its only top level listing or something.

                    We currently have a Processes page which just lists all the processes and a filter to easily select if you need to see only one type of processes, lets them easily navigate,
                    you have a similar search in yours.