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

Detailed search issues when document type selected is INITIATED

    Details

    • Type: Bug Fix Bug Fix
    • Status: Open Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-3133Superuser Search and Detailed search buttons remove entered doc type from search
      KULRICE-5838Modify code which generates SQL for the detailed document search to treat the group ID as a string instead of a number to prevent a type casting issue in Oracle when the SQL is used.
      KULRICE-4321Detailed Doc Search is not returning results if the "document route node" selected
      KULRICE-5744Help link on document search shoudl result to custom document type documentation when a document type is selected
      KULRICE-11969Cannot perform detailed document searches that specify a doc type lacking route nodes
      KULRICE-8717Document Search issue with custom attribute date searches
      KULRICE-1764Document Search does not return all valid results when using a Route Node Name criteria on Detailed Search
      KULRICE-2840Detailed Document Search - Doc status dropdown changed to multi-select. Added ability to search by status category.
      KULRICE-1420Doc Search - clicking Parent Document search on Document Type look up goes to the same Doc Type look up screen.
      KULRICE-3587Document Search will not allow an xml search attribute to use the 'select' (dropdown) type for a Search Attribute
    • Rice Module:
      KEW
    • Application Requirement:
      KFS, KC
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      I was testing this in KC and I noticed some issues.
      1. Steps to recreate: Click on detailed search. Select document status "Initiated". Perform a search and click on one of the document links displayed.
      Actual behavior: A screen is displayed which says "The Document you have selected cannot be opened." and there is a close button. If you click the "close" button, you are redirected to the Rice portal instead of the client portal.
      Desired behavior: The user should be redirected to the client portal.
      2. Click on detailed search, then superuser search. When the options appear, select "INITIATED" again and perform a search. Click on one of the document links displayed.
      Actual behavior: A screen is displayed which says "The Document you have selected cannot be opened." and there is a close button. But there are also additional superuser actions displayed below with cancel and routing options. If you click "Cancel", a stack trace is thrown. None of the buttons work. The following is the stack trace.

      ******************Stack Trace-Only shown when not in production*****************
      java.lang.RuntimeException: post processor caught exception while handling route status change: unable to load document 3385
      	at org.kuali.rice.kew.actions.SuperUserActionTakenEvent.recordAction(SuperUserActionTakenEvent.java:118)
      	at org.kuali.rice.kew.actions.SuperUserCancelEvent.recordAction(SuperUserCancelEvent.java:31)
      	at org.kuali.rice.kew.routeheader.service.impl.WorkflowDocumentServiceImpl.superUserCancelAction(WorkflowDocumentServiceImpl.java:407)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      	at java.lang.reflect.Method.invoke(Method.java:616)
      	at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:318)
      	at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
      	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
      	at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:110)
      	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
      	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
      	at $Proxy254.superUserCancelAction(Unknown Source)
      	at org.kuali.rice.kew.impl.action.WorkflowDocumentActionsServiceImpl$27.doInDocumentBo(WorkflowDocumentActionsServiceImpl.java:856)
      	at org.kuali.rice.kew.impl.action.WorkflowDocumentActionsServiceImpl.executeActionInternal(WorkflowDocumentActionsServiceImpl.java:1358)
      	at org.kuali.rice.kew.impl.action.WorkflowDocumentActionsServiceImpl.superUserCancel(WorkflowDocumentActionsServiceImpl.java:852)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      	at java.lang.reflect.Method.invoke(Method.java:616)
      	at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:318)
      	at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
      	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
      	at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:110)
      	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
      	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
      	at $Proxy145.superUserCancel(Unknown Source)
      	at org.kuali.rice.kew.superuser.web.SuperUserAction.cancel(SuperUserAction.java:160)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      	at java.lang.reflect.Method.invoke(Method.java:616)
      	at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:269)
      	at org.kuali.rice.kns.web.struts.action.KualiAction.dispatchMethod(KualiAction.java:171)
      

      Desired behavior: The superuser actions should not be displayed since the document is only in initiated status??

      Also, the "Close" button is green which seems different from any krad button I have seen. Am I missing some CSS config?

        Issue Links

          Activity

          Hide
          Shannon Hess added a comment -

          For issue 1, when attempting to open up initiated documents before, it would try to load the doc and fail giving a stacktrace. Since the doc url was used in this case the close button would redirect to the portal of the client application. Since the new page is a krad screen, it automatically goes back to the kr portal. I need to check and see if this can somehow be changed. The fact that the button is green is very strange. Working to correct this.

          For issue 2, I'm not able to reproduce this. I always have just the "The Document you have selected cannot be opened" message. Could you let me know a good way to reproduce this problem?

          Thanks,
          Shannon

          Show
          Shannon Hess added a comment - For issue 1, when attempting to open up initiated documents before, it would try to load the doc and fail giving a stacktrace. Since the doc url was used in this case the close button would redirect to the portal of the client application. Since the new page is a krad screen, it automatically goes back to the kr portal. I need to check and see if this can somehow be changed. The fact that the button is green is very strange. Working to correct this. For issue 2, I'm not able to reproduce this. I always have just the "The Document you have selected cannot be opened" message. Could you let me know a good way to reproduce this problem? Thanks, Shannon
          Hide
          Shannon Hess added a comment -

          I was making a silly mistake and now can reproduce issue 2

          Show
          Shannon Hess added a comment - I was making a silly mistake and now can reproduce issue 2
          Hide
          Gayathri Athreya added a comment -

          Hi Shannon, regarding issue 1. Claus made a fix for something similar in KULRICE-8008, they might be related but not sure. For issue2. Did you click the superuser search and then the detailed search? If you scroll all the way down when you see the "cannot be opened" message, you should see it.

          Show
          Gayathri Athreya added a comment - Hi Shannon, regarding issue 1. Claus made a fix for something similar in KULRICE-8008 , they might be related but not sure. For issue2. Did you click the superuser search and then the detailed search? If you scroll all the way down when you see the "cannot be opened" message, you should see it.
          Hide
          Shannon Hess added a comment -

          I committed a fix for the green button and the super user action no longer appear.

          The following issues still remain though:

          1. Still returning to KR portal on close

          2. On the superuser screen, the close button is an option but an error is thrown when the button is selected.

          Show
          Shannon Hess added a comment - I committed a fix for the green button and the super user action no longer appear. The following issues still remain though: 1. Still returning to KR portal on close 2. On the superuser screen, the close button is an option but an error is thrown when the button is selected.
          Hide
          Shannon Hess added a comment -

          Steve,

          Peter suggested that I assign this one over to you since you worked on KULRICE-7292.

          Thanks,
          Shannon

          Show
          Shannon Hess added a comment - Steve, Peter suggested that I assign this one over to you since you worked on KULRICE-7292 . Thanks, Shannon
          Hide
          Shannon Hess added a comment - - edited

          Hello,

          I found out that my fix for preventing the super user actions from appearing will not work for all cases since some actions are valid for document types when the document is in an initiated status.

          I have reverted my change that was made to SuperUser.jsp, so the super user actions will appear again if the document is in initiated status.

          Thanks,
          Shannon

          Show
          Shannon Hess added a comment - - edited Hello, I found out that my fix for preventing the super user actions from appearing will not work for all cases since some actions are valid for document types when the document is in an initiated status. I have reverted my change that was made to SuperUser.jsp, so the super user actions will appear again if the document is in initiated status. Thanks, Shannon
          Hide
          Jessica Coltrin (Inactive) added a comment -

          moving all non-critical 2.1.3 Jiras to 2.1.4

          Show
          Jessica Coltrin (Inactive) added a comment - moving all non-critical 2.1.3 Jiras to 2.1.4

            People

            • Assignee:
              Unassigned
              Reporter:
              Gayathri Athreya
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:

                Structure Helper Panel