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

On submit of Send Adhoc button goes to incident report in Maintenance Document

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.3.0-rc1, 2.3
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-13267Attempting to Adhoc route a document currently ENROUTE throws NPE
      KULRICE-4100send adhoc request button does not validate that a recipient has been entered
      KULRICE-11299Error when submitting incident report form
      KULRICE-4402When using IE, the incident report screen's "close" button behaves just like its "submit" button
      KULRICE-12464Maintenance Document BO Submit Attachment Incident Report ClassCastException LabsTravelAttachment cannot be cast to PersistableBusinessObject
      KULRICE-13871AFT Failure LabsMaintenancePromptBeforeRoutingAft Incident Reports
      KULRICE-9840KRAD Demo Travel Account Maintenance Edit NPE Incident Report
      KULRICE-12669Reload results in incident report after copying certain KRAD maintenance docs
      KULRICE-8604Travel Account Maintenance Document, Parameter Maintenance Document, and Routing Rule Delegation in sampleapp DB Incident Reports on viewing.
    • Rice Module:
      KRAD
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      When a maintenance document routed, the Send Adhoc button is enabled, while submiting the Send Adhoc button application takes to the Incident Report.

      org.springframework.web.HttpRequestMethodNotSupportedException: Request method 'POST' not supported at org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter$ServletHandlerMethodResolver.resolveHandlerMethod(AnnotationMethodHandlerAdapter.java:665) at org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter.invokeHandlerMethod(AnnotationMethodHandlerAdapter.java:431) at org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter.handle(AnnotationMethodHandlerAdapter.java:424) at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:900) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:827) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882) at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:789) at javax.servlet.http.HttpServlet.service(HttpServlet.java:641) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.kuali.rice.krad.web.CharsetFilter.doFilter(CharsetFilter.java:56) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.kuali.rice.kew.web.UserPreferencesFilter.doFilter(UserPreferencesFilter.java:78) at org.kuali.rice.kew.web.UserPreferencesFilter.doFilter(UserPreferencesFilter.java:62) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.kuali.rice.kew.web.UserLoginFilter.doFilter(UserLoginFilter.java:89) at org.kuali.rice.kew.web.UserLoginFilter.doFilter(UserLoginFilter.java:77) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.kuali.rice.kew.web.BootstrapFilterChain.doFilter(BootstrapFilter.java:327) at org.kuali.rice.kew.web.DummyLoginFilter.doFilter(DummyLoginFilter.java:96) at org.kuali.rice.kew.web.DummyLoginFilter.doFilter(DummyLoginFilter.java:55) at org.kuali.rice.kew.web.BootstrapFilterChain.doFilter(BootstrapFilter.java:320) at org.kuali.rice.kew.web.BootstrapFilter.doFilter(BootstrapFilter.java:199) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.kuali.rice.core.web.Log4JContextClearingFilter.doFilterInternal(Log4JContextClearingFilter.java:37) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.kuali.rice.krad.web.filter.HideWebInfFilter.doFilter(HideWebInfFilter.java:69) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.springframework.web.filter.AbstractRequestLoggingFilter.doFilterInternal(AbstractRequestLoggingFilter.java:193) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:987) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:309) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662)

        Issue Links

          Activity

          Hide
          Corey Pedersen (Inactive) added a comment -

          It appears that OLE has specified a methodToCall="sendAdHocRequests" on a maintenance document.
          (Not shown in this jira but probably "OleLicenseRequestMaintenanceDocument.xml")

          The error shown above in the description "org.springframework.web.HttpRequestMethodNotSupportedException: Request method 'POST' not supported at " indicates the controller (probably "OleLicenseRequestController") does not support nor has inherited a method for methodToCall="sendAdHocRequests".

          (org.kuali.rice.krad.web.controller.MaintenanceDocumentController does not support methodToCall="sendAdHocRequests")

          Show
          Corey Pedersen (Inactive) added a comment - It appears that OLE has specified a methodToCall="sendAdHocRequests" on a maintenance document. (Not shown in this jira but probably "OleLicenseRequestMaintenanceDocument.xml") The error shown above in the description "org.springframework.web.HttpRequestMethodNotSupportedException: Request method 'POST' not supported at " indicates the controller (probably "OleLicenseRequestController") does not support nor has inherited a method for methodToCall="sendAdHocRequests". (org.kuali.rice.krad.web.controller.MaintenanceDocumentController does not support methodToCall="sendAdHocRequests")
          Hide
          Corey Pedersen (Inactive) added a comment -

          Additional followup on AdHocRequest functionality needed.

          Show
          Corey Pedersen (Inactive) added a comment - Additional followup on AdHocRequest functionality needed.
          Hide
          Corey Pedersen (Inactive) added a comment -

          sendAdHocRequests functionality will be added for maintenance documents.

          Show
          Corey Pedersen (Inactive) added a comment - sendAdHocRequests functionality will be added for maintenance documents.
          Hide
          Peter Giles (Inactive) added a comment -

          Corey, if I set the mergeWithPageItems property to "true" in the Term-MaintenanceView bean in TermBo.xml, I am able to edit a Term, add ad hoc recipients and route to them (the button I hit is "submit", so the methodToCall is not "sendAdHocRequests"). Not sure if this will be of any assistance, but thought I'd share in case it is.

          Show
          Peter Giles (Inactive) added a comment - Corey, if I set the mergeWithPageItems property to "true" in the Term-MaintenanceView bean in TermBo.xml, I am able to edit a Term, add ad hoc recipients and route to them (the button I hit is "submit", so the methodToCall is not "sendAdHocRequests"). Not sure if this will be of any assistance, but thought I'd share in case it is.
          Hide
          Corey Pedersen (Inactive) added a comment - - edited

          Peter: Parts of my analysis included the following comment from OLE-3847 and its reference to the Ad Hoc button routing to the incident report page. Also this jira's description focusing on "Send Adhoc button" in the title and that the stack trace in this jira is what you would get for methodToCall being used is not defined. Do you still think the resolution is to add sendAdHocRequests to maintenance docs(MaintenanceDocumentController) or is it back to OLE removing the erroneous button from their footer?

          Copied "Juliya Monica added a comment - 09/May/13 8:56 AM

          Yes, that is right. after login as edna add the adhoc recipient and then click on submit. The document will route to the added recipient. As per the framework,the send adhoc button will not work it is redirecting to the incident report.

          Also FYI,
          The Ad Hoc Recipients tab allows you to interrupt the normal workflow routing of a document and include other individuals or groups in its routing path. Ad Hoc Routing does not replace the normal workflow routing of the document; it adds people or groups to the normal routing.

          The Ad Hoc Recipients tab has two sections: Person Requests and Ad Hoc Group Requests. Use one or both of the sections to route the document to an additional person, group, or both."

          Show
          Corey Pedersen (Inactive) added a comment - - edited Peter: Parts of my analysis included the following comment from OLE-3847 and its reference to the Ad Hoc button routing to the incident report page. Also this jira's description focusing on "Send Adhoc button" in the title and that the stack trace in this jira is what you would get for methodToCall being used is not defined. Do you still think the resolution is to add sendAdHocRequests to maintenance docs(MaintenanceDocumentController) or is it back to OLE removing the erroneous button from their footer? Copied "Juliya Monica added a comment - 09/May/13 8:56 AM Yes, that is right. after login as edna add the adhoc recipient and then click on submit. The document will route to the added recipient. As per the framework,the send adhoc button will not work it is redirecting to the incident report. Also FYI, The Ad Hoc Recipients tab allows you to interrupt the normal workflow routing of a document and include other individuals or groups in its routing path. Ad Hoc Routing does not replace the normal workflow routing of the document; it adds people or groups to the normal routing. The Ad Hoc Recipients tab has two sections: Person Requests and Ad Hoc Group Requests. Use one or both of the sections to route the document to an additional person, group, or both."
          Hide
          Corey Pedersen (Inactive) added a comment -

          Testing addition of methodToCall=sendAdHocRequests on People Flow Maintenance document.

          Show
          Corey Pedersen (Inactive) added a comment - Testing addition of methodToCall=sendAdHocRequests on People Flow Maintenance document.
          Hide
          Corey Pedersen (Inactive) added a comment -

          Committed revision 40080. Added methodToCall=sendAdHocRequests to DocumentControllerBase.

          Show
          Corey Pedersen (Inactive) added a comment - Committed revision 40080. Added methodToCall=sendAdHocRequests to DocumentControllerBase.

            People

            • Assignee:
              Corey Pedersen (Inactive)
              Reporter:
              Juliya Monica (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel