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

Sub Fund Reviewer is not displaying Blanket Approved in Route log annotation

    Details

    • Type: Bug Fix Bug Fix
    • Status: Open Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Testing
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-3082Make blanket approval annotations usable on the route log
      KULRICE-14064People Flow does not add an annotation in Route Log
      KULRICE-4756Route Log: approver is showing in the route log instead of the Primary Delegate
      KULRICE-7762Super user approved for two fiscal officers - annotation only showed up for one.
      KULRICE-4083ALLOW_ENROUTE_BLANKET_APPROVE_WITHOUT_APPROVAL_REQUEST_IND doesn't appear to work the way it's being described.
      KULRICE-8043Term specification document remains enroute after blanket approval and user is unable to create any more term specification documents.
      KULRICE-5522Rice Dev: Blanket approve of edit Role document not routing properly
      KULRICE-891Refactor annotations/notes/attachments
      KULRICE-14271Blanket approve displays "Confirm Navigation" dialog
      KULRICE-4407Route Log - detail missing on requested of workgroup
    • Rice Module:
      KEW
    • Application Requirement:
      Rice
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      Created a Travel Document as khuntley in TEM and blanket approved the document.

      The Sub Fund Reviewer node is not displaying the annotation as blanket approved like other approval nodes.

      Created rsmart Jira KualiTEM-1171, but instructed this is a Rice Issue and Foundation Jira should be created.

      See attached screenshot

        Activity

        Hide
        Eric Westfall added a comment -

        If I had to guess on this one, I assume the original error was from Rice 1.0.3.something (not sure which version they were using for TEM but I assume a variant of 1.0.3). You'd have to check with the KFS project to determine if they have a functional version of TEM using Rice 2.0 yet.

        Show
        Eric Westfall added a comment - If I had to guess on this one, I assume the original error was from Rice 1.0.3.something (not sure which version they were using for TEM but I assume a variant of 1.0.3). You'd have to check with the KFS project to determine if they have a functional version of TEM using Rice 2.0 yet.
        Hide
        Matt Sargent added a comment -

        Was worth a try, but no luck there. The problem I'm running into is in the test instances we have, the route log is working fine w/blanket approve. However, in your example it's clearly not, so I was curious what rSmart's comments were on why this would be a Rice issue as opposed to a KFS, TEM, etc. one. Could you have the rSmart ticket assignee comment in this JIRA what they are seeing?

        Show
        Matt Sargent added a comment - Was worth a try, but no luck there. The problem I'm running into is in the test instances we have, the route log is working fine w/blanket approve. However, in your example it's clearly not, so I was curious what rSmart's comments were on why this would be a Rice issue as opposed to a KFS, TEM, etc. one. Could you have the rSmart ticket assignee comment in this JIRA what they are seeing?
        Hide
        Matt Sargent added a comment -

        Thanks Eric, I'll check with KFS as well on that.

        -Matt

        Show
        Matt Sargent added a comment - Thanks Eric, I'll check with KFS as well on that. -Matt
        Hide
        Dawn Bodle added a comment -

        The rSmart tickets all show 'unassigned' when closed. However, Warner Onstine was the developer that indicated it's a Rice issue.
        Comments from the Jira are below:

        Warner Onstine added a comment - 14/Feb/12 2:28 PM
        Not sure why it works this way but this is part of Rice. If you try blanket approving any document that has SubFund Reviewer node you get the same annotation. Please look at doc # 3715 (a Non-Check Disbursement which is incredibly easy to create and blanket approve) to see what I'm talking about.
        If this needs to be fixed then file a foundation issue, link and close this issue to the foundation issue.

        Show
        Dawn Bodle added a comment - The rSmart tickets all show 'unassigned' when closed. However, Warner Onstine was the developer that indicated it's a Rice issue. Comments from the Jira are below: Warner Onstine added a comment - 14/Feb/12 2:28 PM Not sure why it works this way but this is part of Rice. If you try blanket approving any document that has SubFund Reviewer node you get the same annotation. Please look at doc # 3715 (a Non-Check Disbursement which is incredibly easy to create and blanket approve) to see what I'm talking about. If this needs to be fixed then file a foundation issue, link and close this issue to the foundation issue.
        Hide
        Matt Sargent added a comment -

        KFS is still in the process of working on 2.0 and TEM so we'll have to hold off on this until we can verify against that.

        Show
        Matt Sargent added a comment - KFS is still in the process of working on 2.0 and TEM so we'll have to hold off on this until we can verify against that.

          People

          • Assignee:
            Unassigned
            Reporter:
            Dawn Bodle
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Structure Helper Panel