Details
-
Type:
Improvement
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.2
-
Fix Version/s: Backlog
-
Component/s: Development, Roadmap
-
Security Level: Public (Public: Anyone can view)
-
Labels:
-
Rice Module:KRAD
-
KRAD Feature Area:Inquiry, Lookup, Maintenance
-
Application Requirement:KS
-
KAI Review Status:Not Required
-
KTI Review Status:Not Required
Description
From KOLE: Our use best use case is for Patron-Driven Acquisitions or Patron Circulation. A User would enter all transactional information into the PO or circulation e-doc or interface, and need to select or input the Patron's information. This would initiate through a Lookup, search, and return value (current Lookup function). But, if the Patron/User is not found, we would like to be able to jump to a Maintenance doc or other Patron UI, enter the Patron information, save, and return the value/select for input into the transactional edoc (combined transactional and maintenance actions in simplified views and fewer steps than today).
Attachments
Issue Links
- relates to
-
KRRM-141 KRAD Phase 3 - Complete core features needed by KS
-
- Resolved
-
from William: Could this be accomplished with the "Inner Views" functionality? Or resolved by keeping user's data in the transaction form while they go to a maintenance doc to create a new record?