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

Travel sample app / Fiscal Officer maintenance doc needs help

    Details

    • Type: Bug Fix Bug Fix
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.0.3
    • Fix Version/s: Backlog
    • Component/s: Development
    • Labels:
    • Similar issues:
      KULRICE-8564Travel Account Maintenance (New) JS exception on Fiscal Officer Accounts Add button - Uncaught TypeError: Cannot call method 'element' of undefined http://env1.rice.kuali.org/krad/min/scripts/krad_2.2.0-rc1-r35849.min.js 439
      KULRICE-1356Error adding attachment in Travel Fiscal Officer Maintenance Document.
      KULRICE-4753Add MaintainableCollectionDefinition to TravelApp Fiscal Officer Maint Doc
      KULRICE-4777Fix workflow for Travel Request (sample travel app)
      KULRICE-12382Peopleflow Summery Type KR-SAP Sample Type utilizes deleted Travel Fiscal Officer Id
      KULRICE-8545Travel Account Maintenance (New) Document: Fiscal Officer Accounts Section Issue
      KULRICE-5493Rice Dev: KRAD, Sample Travel App bombing with Data Dictionary errors
      KULRICE-9484Review Travel App & KRMS screens for Look & Feel changes
      KULRICE-11974AFT Failure DemoTravelAccountMaintenanceEditAft.testDemoTravelAccountMaintenanceEditFiscalOfficerBookmark Fiscal Officer Not Changed
      KULRICE-8546Travel Account Maintenance (Edit): Deleting a Fiscal Officer Account gives error
    • Rice Module:
      KNS
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      • unable to "create new" successfully, or edit an existing Fiscal Officer
      • Weird unlabeled and unusable field in maintenance forms
      • can't add or remove accounts
      • the doc handler links (doc search) for Fiscal Officer docs don't work.

        Issue Links

          Activity

          Hide
          Peter Giles (Inactive) added a comment -

          See comments on subtasks of linked issue for more details

          Show
          Peter Giles (Inactive) added a comment - See comments on subtasks of linked issue for more details
          Hide
          Garey Taylor added a comment -

          You should* be able to create Fiscal Officers. I updated that one on the 13th when I was testing out maintainable collections.
          Basically, the FO was missing a docType in the Maintenance Doc so I set it to the default "riceDocument". I updated FiscalOfficerMaintenanceDocument.xml.

          Show
          Garey Taylor added a comment - You should* be able to create Fiscal Officers. I updated that one on the 13th when I was testing out maintainable collections. Basically, the FO was missing a docType in the Maintenance Doc so I set it to the default "riceDocument". I updated FiscalOfficerMaintenanceDocument.xml.
          Hide
          Peter Giles (Inactive) added a comment - - edited

          There is actually a docType called FiscalOfficerMaintenanceDocument in our data set. I think you can just edit it to make it a child of RiceDocument so that with the default permissions a "create new" button shows up. In any case, submitting a new fiscal officer didn't work. It appeared to, since it said at the top of the doc that "Document was successfully submitted", but then the exceptions started flooding the Rice server's log, and the document status got stuck at ENROUTE in the PreRoute node.

          Show
          Peter Giles (Inactive) added a comment - - edited There is actually a docType called FiscalOfficerMaintenanceDocument in our data set. I think you can just edit it to make it a child of RiceDocument so that with the default permissions a "create new" button shows up. In any case, submitting a new fiscal officer didn't work. It appeared to, since it said at the top of the doc that "Document was successfully submitted", but then the exceptions started flooding the Rice server's log, and the document status got stuck at ENROUTE in the PreRoute node.
          Hide
          Peter Giles (Inactive) added a comment -

          BTW, I can imagine this being a DB platform difference if it did in fact work for you. The jdbc exception I'm seeing is "com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Column 'ACCT_FO_USER_NAME' specified twice ". Maybe Oracle doesn't mind this weirdness, but MySQL chokes on it.

          Show
          Peter Giles (Inactive) added a comment - BTW, I can imagine this being a DB platform difference if it did in fact work for you. The jdbc exception I'm seeing is "com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Column 'ACCT_FO_USER_NAME' specified twice ". Maybe Oracle doesn't mind this weirdness, but MySQL chokes on it.

            People

            • Assignee:
              Unassigned
              Reporter:
              Peter Giles (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Structure Helper Panel