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

Improve Capabilities of Exception Routing

    Details

    • Type: Rice Enhancement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Component/s: KEW
    • Labels:
      None
    • Rice Theme:
      Kuali Application Business Drivers
    • Priority Score:
      6
    • Functional Justification :
      Hide
      Functionality has been requested as follows:

      1) Allow for a workflow transaction to be "forced" into exception routing based on some condition. Currently it is only possible to do this is some sort of internal error is raised during processing of the document.
      2) Customize how long it takes a document to transition into exception routing when faced with failure or error scenarios.
      3) Define a custom process "flow" for exception cases (i.e. allow an exception document to go through two levels of review prior to being submitted back to the workflow engine for a retry).

      You can see that all of these have a functional implication for those parties who administer and handle exception routing cases on workflow transactions.
      Show
      Functionality has been requested as follows: 1) Allow for a workflow transaction to be "forced" into exception routing based on some condition. Currently it is only possible to do this is some sort of internal error is raised during processing of the document. 2) Customize how long it takes a document to transition into exception routing when faced with failure or error scenarios. 3) Define a custom process "flow" for exception cases (i.e. allow an exception document to go through two levels of review prior to being submitted back to the workflow engine for a retry). You can see that all of these have a functional implication for those parties who administer and handle exception routing cases on workflow transactions.
    • Technical Justification:
      It makes sense to allow developers to code up document processing such that it forces a document into exception routing if an issue is encountered and it is known that a retry of the document is not going to "fix" the problem.
    • Impact if not Implemented:
      The impact if this is not implemented just relates to continued inflexibility in the way that exception processing is handled in the workflow engine.
    • Priority - KFS:
      Medium
    • Priority - KC:
      Medium
    • Priority - KS:
      Uncertain - Need More information
    • Priority - Rice:
      Medium
    • Theme:
      Kuali Application Business Drivers
    • Application Impact:
      Low
    • Effort Estimate:
      Very Low ~ 50 hrs

      Description

      This includes various enhancements, see linked issues.

      Summary of Work Involved: This small set of enhancements would allow exception routing to be more configurable by an application to define when a document goes into or attempts to get out of exception routing. Definitions for forcing a document into exception based on some condition other than an internal error, how many retries a document does before going into exception, and how long to wait between retries are being requested. Originally a lager task of allowing custom routing/flow of exception documents (based on document type, document data, etc.) was part of this task, but was moved to its own roadmap item (KRRM-119) since these should be considered separate tasks.

        Attachments

          Issue Links

            Activity

            Hide
            cfairlie Cath Fairlie (Inactive) added a comment -

            KS was not sure if this was exception routing due to error processing or if it was exception routing caused by business conditions or functionality. More information is requested.

            Show
            cfairlie Cath Fairlie (Inactive) added a comment - KS was not sure if this was exception routing due to error processing or if it was exception routing caused by business conditions or functionality. More information is requested.
            Hide
            ewestfal Eric Westfall added a comment -

            This is exception routing due to errors that occur during routing of a document. Since that work happens asynchronously, KEW will put the document in the Action List of members of an exception workgroup so they can determine why the document went into exception routing and what needs to be done to resolve it. This could be caused by various factors, issues communicating with external sources (like the database), bugs in custom routing components, document policies forcing the document into exception routing because some condition has occurred, etc.

            Show
            ewestfal Eric Westfall added a comment - This is exception routing due to errors that occur during routing of a document. Since that work happens asynchronously, KEW will put the document in the Action List of members of an exception workgroup so they can determine why the document went into exception routing and what needs to be done to resolve it. This could be caused by various factors, issues communicating with external sources (like the database), bugs in custom routing components, document policies forcing the document into exception routing because some condition has occurred, etc.
            Hide
            ewestfal Eric Westfall added a comment -

            I can champion this one from an IU perspective. The items linked here were specific requests from IU developers working on Rice-based applications.

            Show
            ewestfal Eric Westfall added a comment - I can champion this one from an IU perspective. The items linked here were specific requests from IU developers working on Rice-based applications.
            Hide
            ewestfal Eric Westfall added a comment -

            I want to affirm requirements of what functionality will be provided by this roadmap item. Here is what I have assembled based on the description and comments:

            1) Allow for a workflow transaction to be "forced" into exception routing based on some condition. Currently it is only possible to do this is some sort of internal error is raised during processing of the document.
            2) Customize (at the document type level) how many retries are performed against a document before it transitions into exception routing when faced with failure or error scenarios.
            3) Customize (at the document type level) how long the document will wait between retries when faced with failure or error scenarios.
            4) Define a custom process "flow" for exception cases (i.e. allow an exception document to go through two levels of review prior to being submitted back to the workflow engine for a retry, or allow for it to route to different exception responsibilities based on document data).

            Is this list complete and does it encompass the desired behavior for the first version of this functionality?

            Show
            ewestfal Eric Westfall added a comment - I want to affirm requirements of what functionality will be provided by this roadmap item. Here is what I have assembled based on the description and comments: 1) Allow for a workflow transaction to be "forced" into exception routing based on some condition. Currently it is only possible to do this is some sort of internal error is raised during processing of the document. 2) Customize (at the document type level) how many retries are performed against a document before it transitions into exception routing when faced with failure or error scenarios. 3) Customize (at the document type level) how long the document will wait between retries when faced with failure or error scenarios. 4) Define a custom process "flow" for exception cases (i.e. allow an exception document to go through two levels of review prior to being submitted back to the workflow engine for a retry, or allow for it to route to different exception responsibilities based on document data). Is this list complete and does it encompass the desired behavior for the first version of this functionality?
            Hide
            sagee Sandra Agee (Inactive) added a comment -

            This scope is confirmed with slight addition

            Also customize, how many times the document waits and how long the documents waits.

            Research to answer the question on "What should happen once exception routing fall back occurs"

            Show
            sagee Sandra Agee (Inactive) added a comment - This scope is confirmed with slight addition Also customize, how many times the document waits and how long the documents waits. Research to answer the question on "What should happen once exception routing fall back occurs"
            Hide
            ewestfal Eric Westfall added a comment -

            Created 3 sub-tasks and then moved item number 4 on defining a custom process flow to KRRM-119 since I think it can be considered separate from the others and (I believe) not as high priority.

            Show
            ewestfal Eric Westfall added a comment - Created 3 sub-tasks and then moved item number 4 on defining a custom process flow to KRRM-119 since I think it can be considered separate from the others and (I believe) not as high priority.
            Hide
            ewestfal Eric Westfall added a comment -

            Reducing estimate to "Very Low ~ 50 hrs" after moving out the exception flow item to KRRM-119

            Show
            ewestfal Eric Westfall added a comment - Reducing estimate to "Very Low ~ 50 hrs" after moving out the exception flow item to KRRM-119
            Hide
            masargen Matt Sargent added a comment -

            Gary Prohaska - if it’s only 50 hours and it provides benefit let’s do it!

            Show
            masargen Matt Sargent added a comment - Gary Prohaska - if it’s only 50 hours and it provides benefit let’s do it!

              People

              • Assignee:
                ewestfal Eric Westfall
                Reporter:
                ewestfal Eric Westfall
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated: