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

Allow for execution of Super User functions on a document that is SAVED or INITIATED

    Details

    • Similar issues:
      KULRICE-1744Implement proper Super User support in EDocLite
      KULRICE-8300problems with implementation of super user tab
      KULRICE-12866Implement Super User Functionality in KRAD
      KULRICE-14165Super User Validations on Documents
      KULRICE-7799Create a separate permission for accessing the new super user tab
      KULRICE-747Allow for Super User actions to be taken against FINAL documents
      KULRICE-1236If a user has an FYI or ACK request on an initiated or saved document, they are not allowed to take action on it
      KULRICE-8097Validation is not done on document when completing a doc via the Super User screen; Any changes made on the document in the super user screen are not saved before the document is completed.
      KULRICE-1465Add a checkbox to the super user screen which indicates whether or not the post processor should be run when executing the super user action
      KULRICE-782Make super user and blanket approve workgroups both inheritable and optional in DocumentType XML
    • Rice Module:
      KEW

      Description

      For some reason we don't allow super user actions on documents that are in the SAVED or INITIATED state. This makes it impossible for a super user to take a SAVED document with a complete request to the initiator and route it.

        Issue Links

          Activity

          Hide
          Eric Westfall added a comment -

          We need to make sure that if a SAVED document has a request, that it can be taken by the super user (this should cause a route automatically because of the code in the COMPLETE action, but double-check that). Also, if a document is saved and it has adhoc requests on it. It should be possible for the super user to take those actions as well.

          Also, if initiated, super user should be able to cancel it.

          One other to check:

          Make sure when the document is FINAL, that it's possible for the super user to take FYI's for someone.

          Show
          Eric Westfall added a comment - We need to make sure that if a SAVED document has a request, that it can be taken by the super user (this should cause a route automatically because of the code in the COMPLETE action, but double-check that). Also, if a document is saved and it has adhoc requests on it. It should be possible for the super user to take those actions as well. Also, if initiated, super user should be able to cancel it. One other to check: Make sure when the document is FINAL, that it's possible for the super user to take FYI's for someone.
          Hide
          Eric Westfall added a comment -

          Most of the logic that is checking statuses is in the JSP I believe.

          Show
          Eric Westfall added a comment - Most of the logic that is checking statuses is in the JSP I believe.
          Hide
          David Elyea added a comment -

          As part of this change i moved most of the status checking into the SuperUserForm so that the JSP holds very little logic. Some of the methods were existing methods and others were created new for my changes. Here is a list of the Super User Action cases i either implemented or wrote unit tests to check for:

          1) Document in INITIATED status: Super user can Cancel a document in Initiated status

          2) Document in SAVED status:
          A) Super user can take the "Complete" request that is generated by the Save action and document will route as a result of the super user action taken
          B) Super user can take action on Adhoc Requests on document and document will not route as a result
          C) Super user can route Adhoc Requests requests to users

          3) Document in PROCESSED status: Super user can take acknowledge and fyi requests

          4) Document in FINAL status: Super user can take fyi requests

          Show
          David Elyea added a comment - As part of this change i moved most of the status checking into the SuperUserForm so that the JSP holds very little logic. Some of the methods were existing methods and others were created new for my changes. Here is a list of the Super User Action cases i either implemented or wrote unit tests to check for: 1) Document in INITIATED status: Super user can Cancel a document in Initiated status 2) Document in SAVED status: A) Super user can take the "Complete" request that is generated by the Save action and document will route as a result of the super user action taken B) Super user can take action on Adhoc Requests on document and document will not route as a result C) Super user can route Adhoc Requests requests to users 3) Document in PROCESSED status: Super user can take acknowledge and fyi requests 4) Document in FINAL status: Super user can take fyi requests

            People

            • Assignee:
              David Elyea
              Reporter:
              Eric Westfall
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Due:
                Created:
                Updated:
                Resolved:

                Structure Helper Panel