Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-12495

Task Resolution Screen

    XMLWordPrintable

    Details

    • Type: User story
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.8
    • Component/s: Workflow

      Description

      See the attached screenshots.

      • As a user being assigned a task,from the workflow dashboard, I can click on a "Process task" button. Instead of bringing me to the Document view, it displays, within the left "Workflow" tab, a task resolution view. This task resolution view is based on a grid layout and displays:
        • The list of documents that are bound to the workflow related to the task. I must be able to download the file or preview it, or browse the document.
        • The task informations
        • The task form and user actions

      From that view, I can also:

        • see the current workflow graph
        • re-assign
        • delegate
        • go back to the previous screen
      • From the document view, when I am assigned a task, I can see it from the document (I just see a content view with the same kind of information than on the tasks dashboard. I can "process" a task from there. In that case, it changes the central view, but I stay on the document view, with tree on the left (same like the export view)
      • As a user having a task assigned to me on the same workflow instance right after I started the workflow or resumed a task, the system directly redirect me to the next task resolution screen.

      There is a default task-resolution view, and it is possible to override it from Studio for a specific node of the workflow.
      From Studio, on the configuration screen of a node, on the general tab, I can choose a Tab feature instance that will be used for configuring my screen.
      If I want to display the document list, I will use the content view widget, with a specific binding for the data list to display (We may add a specific widget in the future for having the binding automated, but that's not necessary now).
      I have a task widget that I can use for displaying the task info, and a "task form" widget for the data.

      In the future (not on the first shot), I'll also want to be able to leverage the following information for designing my view:

      • Document[0] bound to the route and its metadata (an easy way to provide a view layout when I know that my workflow is with one document only, instead of doing a listing layout with one row)
      • TaskInfo : useful to have access to it especially when on a multi-task node (but let's do it later with more spec)

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: