Details

    • Type: Rice Enhancement
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Component/s: KEW
    • Labels:
      None
    • Rice Theme:
      Kuali Application Business Drivers
    • Priority Score:
      12
    • Functional Justification :
      Hide
      This feature facilitates the movement of documents through their workflow, limiting the amount of time a document will/can stay assigned to one individual before either escalating to another source due to inaction or to another predefined individual based on what makes sense for that document type.

      Here is one Use Case for such a feature: A document is created and routes to an Approver who is on vacation for two weeks. Using this escalation feature, the document type could be set to auto-escalate if no action has been taken within a 3-5 business days and would route to the next defined individual (either to another Approver or to the original Approver's Manager, for example).
      Show
      This feature facilitates the movement of documents through their workflow, limiting the amount of time a document will/can stay assigned to one individual before either escalating to another source due to inaction or to another predefined individual based on what makes sense for that document type. Here is one Use Case for such a feature: A document is created and routes to an Approver who is on vacation for two weeks. Using this escalation feature, the document type could be set to auto-escalate if no action has been taken within a 3-5 business days and would route to the next defined individual (either to another Approver or to the original Approver's Manager, for example).
    • Impact if not Implemented:
      Hide
      Actions list of users will continue to grow with stale documents and technical or other resources will be needed to clean up or push through documents for time sensitive processes wasting valuable time. Applications will need to create their own process for handling these situations, taking away development time. Escalation is a common function of other workflow engines, KEW will be seen as lacking and could lose adoption due to this.
      Show
      Actions list of users will continue to grow with stale documents and technical or other resources will be needed to clean up or push through documents for time sensitive processes wasting valuable time. Applications will need to create their own process for handling these situations, taking away development time. Escalation is a common function of other workflow engines, KEW will be seen as lacking and could lose adoption due to this.
    • Priority - KFS:
      Medium
    • Priority - KC:
      Medium
    • Priority - KS:
      Critical
    • Priority - Rice:
      Medium
    • Theme:
      Kuali Application Business Drivers
    • Application Impact:
      No Impact
    • Effort Estimate:
      Low ~ 200 hrs

      Description

      UC Irvine is currently using an engine that supports escalation (i.e. a document sits in a particular person's "Action List" for a period of time and is then automatically escalated to another individual after that period of time has elapsed).

      This would be a good feature to add to our engine and we should determine what specific features we would want to provide with this.

      Summary of Work Involved: KEW relies on user interaction to fulfill generated action requests. Be it an individual accessing their action list to approve or acknowledge an document, a delegate doing the same, or a super user taking action on behalf of an individual should the situation arise. While this works for the majority of cases, there are times where documents are stuck waiting for action due to inactivity. This slows down the flow of the document and can interrupt necessary downstream processing. In KEW, this feature would offer the option for applications to dictate additional notification and/or the movement of documents through their workflows, limiting the amount of time a document can stay assigned to one action request, before escalation to another based on a set of parameters that make the most sense for that document type. We looked at this for previous Rice release and some analysis was done, for that please see https://wiki.kuali.org/x/8SOREg

        Attachments

          Issue Links

            Activity

            Hide
            sagee Sandra Agee (Inactive) added a comment -

            High Level Scope
            -Allow each document type to have a default Path
            -Each to be configurable based on escalation conditions as it moves from node to node
            -configurable for the amount of time
            -configurable for the types of actions
            -Ability to Set SLA's/Thresholds
            _Ability to have action reminders
            -Ability to e-mail/notify next person in process and re-direct notification
            -Automatically remove from individual action list and route to next/designated person
            -Accurately reflect route log on audit trail
            -Reverse of process (bus scenario may need to be proved out)
            -Ability to escalate based on a "Point in Time"

            Point in Time Event Business Scenario:

            Time sheets are quartz batch processed. Time sheets are automatically routed for approval. If a manager neglects to approve "The Point N Time" service will perform batch job on all time sheets, regardless of where they are in the process, at designated time.

            Show
            sagee Sandra Agee (Inactive) added a comment - High Level Scope -Allow each document type to have a default Path -Each to be configurable based on escalation conditions as it moves from node to node -configurable for the amount of time -configurable for the types of actions -Ability to Set SLA's/Thresholds _Ability to have action reminders -Ability to e-mail/notify next person in process and re-direct notification -Automatically remove from individual action list and route to next/designated person -Accurately reflect route log on audit trail -Reverse of process (bus scenario may need to be proved out) -Ability to escalate based on a "Point in Time" Point in Time Event Business Scenario: Time sheets are quartz batch processed. Time sheets are automatically routed for approval. If a manager neglects to approve "The Point N Time" service will perform batch job on all time sheets, regardless of where they are in the process, at designated time.
            Hide
            ewestfal Eric Westfall added a comment -

            Based on the description of work here, I'm increasing estimate to Low ~200 hours.

            Show
            ewestfal Eric Westfall added a comment - Based on the description of work here, I'm increasing estimate to Low ~200 hours.
            Hide
            manoj.rawat Manoj Rawat (Inactive) added a comment -

            OLE Jira https://jira.kuali.org/browse/OLE-2719 relying on this task/functionality.

            Show
            manoj.rawat Manoj Rawat (Inactive) added a comment - OLE Jira https://jira.kuali.org/browse/OLE-2719 relying on this task/functionality.
            Hide
            masargen Matt Sargent added a comment -

            Gary Prohaska - Question: how would the parameters be configured/managed for escalation? Any chance KRMS could play a role?

            Show
            masargen Matt Sargent added a comment - Gary Prohaska - Question: how would the parameters be configured/managed for escalation? Any chance KRMS could play a role?
            Hide
            kymber Kymber Horn added a comment -

            Removing assignees that are no longer members of ARC. Current members of ARC will be asked to review and claim unassigned Roadmap items prior to our next voting cycle.

            Show
            kymber Kymber Horn added a comment - Removing assignees that are no longer members of ARC. Current members of ARC will be asked to review and claim unassigned Roadmap items prior to our next voting cycle.

              People

              • Assignee:
                masargen Matt Sargent
                Reporter:
                ewestfal Eric Westfall
              • Votes:
                4 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: