[KULRICE-5168] Handle Context Attributes BOs in ContextBoService Created: 26/May/11  Updated: 23/Feb/12  Resolved: 16/Jun/11

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

Type: Task Priority: Critical
Reporter: Daniel Seibert (Inactive) Assignee: Daniel Seibert (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 2 days
Time Spent: Not Specified
Original Estimate: 2 days

Issue Links:
Relate
is related to KULRICE-5169 Consistent KRMS entity attributes Closed
Similar issues:
KULRICE-5169Consistent KRMS entity attributes
KULRICE-14126Transactional documents should be able to store extended attributes automatically
KULRICE-14060AgendaEditor: Attribute query for context field doesn't work.
KULRICE-5202Active Indicator on KRMS entities
KULRICE-10439AttributeSecurity hide attribute is not handled correctly
KULRICE-8651There are two services that serialize BOs to XML and they have different configurations
KULRICE-5245Fix context selection so that it can query on multiple attributes
KULRICE-1681Create KOM DTOs in the kom-api module and move BOs to the kom module
KULRICE-1801when using PersistableBusinessObjectValuesFinder, inquiries blow up (NPE) if the inquiryFields refers to the local BOs attribute field instead of the reference BOs attribute
KULRICE-5307Create KRMS Attribute Definition Lookup Screen
Rice Module:
KRMS
Application Requirement:
Rice
KAI Review Status: Not Required
KTI Review Status: Not Required

 Comments   
Comment by Daniel Seibert (Inactive) [ 08/Jun/11 ]

Also adding context attributes at api layer ContextDefinition, ContextDefinitionContract. At api layer, attributes will be represented as a Map<String,String> of name/value pairs.

Comment by Daniel Seibert (Inactive) [ 09/Jun/11 ]

Refactored attribute handling. See also KULRICE-5169

Comment by Jessica Coltrin (Inactive) [ 23/Feb/12 ]

Closing since these items are now in the release notes.

Generated at Thu Jul 09 20:12:06 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.