[KULRICE-3156] "Viewer Network ID" field on Detailed Search won't find
documents routed to users as part of a workgroup but should Created: 29/May/09 Updated:
17/Aug/09 Resolved: 24/Jun/09
Status:
Project:
Component/s:
Affects
Version/s:
Fix Version/s:
Closed
Kuali Rice Development
Development
None
Type:
Reporter:
Resolution:
Labels:
Remaining
Estimate:
Time Spent:
Original
Estimate:
Bug Fix
Ailish Byrne
Fixed
None
Not Specified
Issue Links:
Duplicate
Similar issues:
KULRICE-1272 On the Workgroup create/edit page when a lookup is
used to find a user/group for the AdHoc Route section
the Workgroup Entry page does not function
KULRICE-5867 Make it so that document does not crash if an invalid
network ID is passed in for an eDocLite field.
KULRICE-1162 Ad Hoc Routing - Clarify Error message when User or
Workgroup is not active (vs invalid)
KULRICE-636 Simple Message - User Recipients & Workgroup
Recipients should be an entry field with search
capabilities, similar to Ad Hoc routing in KFS
KULRICE-2616 Document Search by "Approver Network ID" does not
include Blanket Approvers
KULRICE-943 Update workgroup documentation to include Workgroup
types and configuration
KULRICE-1113 Document the Workgroup Type Lookup screen
KULRICE-1764 Document Search does not return all valid results when
using a Route Node Name criteria on Detailed Search
KULRICE-7045 Group Viewer ID is mistakenly included on the "basic"
doc search
1.0, KFS Release 3.0
Priority:
Assignee:
Votes:
Critical
Garey Taylor
0
Not Specified
Not Specified
KULRICE-809
Rice Module:
Application
Requirement:
Create Functional Documentation for the Route Log
KEW
KFS
Description
see linked issue
Comments
Comment by Eric Westfall [ 30/May/09 ]
Was this meant to be 0.9.4 or 1.0? Based on the KFSMI comments it sounds like it should be
1.0 instead?
Comment by Ailish Byrne [ 31/May/09 ]
totally was. so sorry eric. thanks for checking
Comment by Eric Westfall [ 11/Jun/09 ]
In order to implement this one, will need to query KIM for group ids of principal with the name
entered into that field. Then doc search will have to construct a large OR based on that
comparing that principal's group ids with the group id of any action requests. Since when
requests are generated to a group, only a single ActionRequest is created that has the group ID
attached to it.
Comment by Garey Taylor [ 24/Jun/09 ]
Code has been committed.
Basically, did exactly what Eric said.
Not sure if it's a problem, but I used "and KREW_ACTN_RQST_T.GRP_ID in (" ...
Is there a problem with using the sql "in" statement?
Comment by Eric Westfall [ 24/Jun/09 ]
No problems with using "IN" since it's ANSI SQL. Thanks Garey.
Comment by Eric Westfall [ 25/Jun/09 ]
Approved by KAI-WG - 06-25-2009
Comment by Eric Westfall [ 17/Aug/09 ]
Bulk change of all Rice 1.0 issues to closed after public release.
Generated at Sun Mar 06 03:34:25 CST 2016 using JIRA 6.1.5#6160sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.