[KULRICE-13077] Investigate Implementing Super User Screen Created: 06/Aug/14  Updated: 16/Jan/15

Status: Open
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: None
Fix Version/s: 2.6
Security Level: Public (Public: Anyone can view)

Type: Task Priority: Major
Reporter: Kristina Taylor (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: Old
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Super User Frame.png    
Similar issues:
KULRICE-8300problems with implementation of super user tab
KULRICE-12866Implement Super User Functionality in KRAD
KULRICE-1744Implement proper Super User support in EDocLite
KULRICE-14165Super User Validations on Documents
KULRICE-747Allow for Super User actions to be taken against FINAL documents
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-7799Create a separate permission for accessing the new super user tab
KULRICE-2811Detailed and super user search links don't show up on Document Search
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-1836Create a Document Type policy which will force documents clicked on in super user search to forward back to the application's doc handler URL
Epic Link: Super User
KAI Review Status: Not Required
KTI Review Status: Not Required
Code Review Status: Not Required
Include in Release Notes?:
Yes
Story Points: 8

 Description   

Currently, when doing a super user search in the doc search, Rice wraps the entire page in an iframe that has all the possible super user actions in it. KFS has reported that the iframe is often used to get errant documents into a better state (say, by cancelling them). This would happen when the document cannot be opened, so the iframe around it was actually more of a feature. We need to figure out some other way to do this as well as distinguishing the Super User screen from the Super User tab (which have different permissions).


Generated at Tue Apr 07 07:34:47 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.