Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-12681

allow customization of role-responsibility action request annotation


    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.3.3
    • Fix Version/s: Backlog
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-8587allow customization of workflow notification annotation
      KULRICE-3337Allow for custom action request labels on ad hoc requests for more than just FYI type requests
      KULRICE-1956KEW could be sending duplicate e-mails for action requests during a blanket approval of a document
      KULRICE-3336In some cases an incorrect action request label is being used for action list items based on changes made for the 'custom' action request labelling
      KULRICE-2741Create unit tests that test custom action request labels
      KULRICE-3718Allow Ad Hoc action requests on documents with no route nodes
      KULRICE-7659SuperUser Action Tab Annotation Not Being Applied to All Lines
      KULRICE-2013ability to define custom action request types and map them to the behavior of existing action request types
      KULRICE-7137Bug on Action List - Action Requested Label Blank after super user approve action
      KULRICE-8761CONTRIB: A person performing COMPLETE action should not be allowed to add more complete request adhoc nodes
    • Rice Module:
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:


      I would like to be able to customize the generation of annotations in our route log. ActionRequestFactory.addRoleResponsibilityRequest(..) generates an annotation like "KC-WKFLW COI". That is not very human-friendly. It is hard to override this behavior because ActionRequestFactory is instantiated within RoleRouteModule. If ActionRequestFactory were a Spring bean and the generation of the annotation were refactored into a separate protected method, I could more easily override this behavior.


        There are no comments yet on this issue.


          • Assignee:
            Ken Geis
          • Votes:
            0 Vote for this issue
            1 Start watching this issue


            • Created:

              Structure Helper Panel