[KULRICE-6015] Document the various Rice KIM permissions Created: 20/Nov/08  Updated: 12/Aug/13  Resolved: 15/May/13

Status: Closed
Project: Kuali Rice Development
Component/s: Documentation
Affects Version/s: None
Fix Version/s: 2.3

Type: Task Priority: Major
Reporter: Eric Westfall Assignee: Grant Trudel (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
discovered by KULRICE-2415 implement KR-WKFLW permission and res... Closed
is relied upon by KULRICE-6157 Document the use of "PreRoute" in doc... Closed
Similar issues:
KULRICE-6436Tune ehcache configuration for the various rice modules
KULRICE-3075Fix various pieces of missing KIM configuration and data
KULRICE-6130Document various "validate" methods on KimTypeService
KULRICE-3467Install document types for the KIM permission and responsibility documents
KULRICE-7090Documentation: expand documentation in KIM UG for delivered Permission Templates
KULRICE-7509Rice KIM documents stay editable after submission
KULRICE-10772Support "Use Transactional Document" permission in KRAD
KULRICE-7185Optimization of KIM Permission Checks
KULRICE-13211Investigate attachmentTypeCode and KIM Permissions.
KULRICE-9537Document the approach for conversion to krad-data of the various internal Rice modules
Rice Module:
Include in Release Notes?:


We need to document which KIM permissions need to be set up related to Document Types. See KULRICE-2415 for more details. Also, see the implementation of DocumentTypePermissionService to see how these KIM permissions work with the legacy Document Type Policies and other existing behavior. Of this needs to be documented.

Comment by Eric Westfall [ 26/Nov/08 ]

Also be sure to document the usage and default behavior of the KIM_PRIORITY_ON_DOC_TYP_PERMS_IND system parameter.

Comment by Mike Calhoun (Inactive) [ 29/Jun/09 ]

Bob, I believe you are already addressing this issue.

Comment by Mike Calhoun (Inactive) [ 04/Aug/09 ]

not currently being addressed

Comment by Eric Westfall [ 13/Aug/09 ]

I may try and hit this myself with the comments that Jonathan sent me on the KIM docs. If I can't get to it then i'll set fix version to 1.0.0_01.

Comment by Jeremy Hanson [ 03/Feb/10 ]

Eric, are you still planning on doing this or should I reassign?

Comment by Eric Westfall [ 24/Aug/10 ]

Also, in a recent email exchange with Jonathan, I was trying to figure out why when I submit a document, after I submit it, all of the fields still show up on the screen as editable. Instead, in KFS they all show up as read-only (which should be how it should work). He said you need a permission like the following:

Edit Document (KR-NS) Edit Document (KFS-SYS) Route Node Name = Adhoc, Route Status Code = R KR-WKFLW Approve Request Recipient
Comment by Grant Trudel (Inactive) [ 15/May/13 ]

Delivered permissions can be found in the Permission chapter of the KIM guide, in the subsection Delivered Permission Templates.

Generated at Thu Apr 09 18:59:49 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.