Uploaded image for project: 'Kuali Rice Roadmap'
  1. Kuali Rice Roadmap
  2. KRRM-124

Implement a GUI for Designing KEW Processes

    Details

    • Type: Rice Enhancement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Component/s: KEW
    • Labels:
      None
    • Rice Theme:
      Usability
    • Priority Score:
      0
    • Impact if not Implemented:
      Either technical or knowledgable super-users will continue to be relied upon to setup, maintain, and interpret document flows. KEW will fall behind and look basic in comparison to other workflow tools that provide a rich, enduser friendly, interface.
    • Priority - KFS:
      No Priority
    • Priority - KC:
      No Priority
    • Priority - KS:
      No Priority
    • Priority - Rice:
      No Priority
    • Effort Estimate:
      Very High ~ 2500 hrs

      Description

      In order to really nail down what this would look like, I think the first step would be to research some of the other such editors that exist out there to determine if we can utilize ideas from those other editors. Additionally, there are some important decision that would need to be made:

      1) Would we try to use an existing tool and adapt to our workflow configuration or build our own from scratch?
      2) If we build our own, how would it be delivered? As a web-based application? A desktop application? A plugin into some other tool (like an IDE)?
      3) If it's web-based, would it require enhancements to KRAD in order to be able to implement the desired functionality?
      4) How should the user experience work? We will likely be unsuccessful if it's as complicated to build a KEW-like process with our editor as it would be if trying to do something similar with a BPEL tool.
      5) Where does this tool live? Is it deployed server side with the KEW services? Is it a separate application which simply integrates with the KEW services?
      6) How do we allow for this tool to be extensible so that we plug additional functionality into it (the workflow engine itself is fairly pluggable, so this complicates building a general-purpose GUI for it).

      Those are just a few of the questions we would need to answer. I think we would want to emply a UX person and a GUI designer to help us with this if we were going to build our own.

        Attachments

          Issue Links

            Activity

            Hide
            ewestfal Eric Westfall added a comment - - edited

            I set the estimate on this as "Very High ~ 2500 hrs" to represent the fact that we don't know enough information yet to accurately estimate this item, although we know it's going to be a large amount of work.

            Show
            ewestfal Eric Westfall added a comment - - edited I set the estimate on this as "Very High ~ 2500 hrs" to represent the fact that we don't know enough information yet to accurately estimate this item, although we know it's going to be a large amount of work.
            Hide
            ewestfal Eric Westfall added a comment -

            This issue was broken off from KRRM-51.

            Show
            ewestfal Eric Westfall added a comment - This issue was broken off from KRRM-51 .

              People

              • Assignee:
                sjc37 Sarah Christen (Inactive)
                Reporter:
                ewestfal Eric Westfall
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated: