[KULRICE-8544] Travel Account Maintenance (New) Document: Account Number issues Created: 15/Nov/12  Updated: 21/Mar/13  Resolved: 05/Dec/12

Status: Closed
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: 2.2.0-rc1
Fix Version/s: 2.2.1
Security Level: Public (Public: Anyone can view)

Type: Bug Fix Priority: Major
Reporter: Matt Sargent Assignee: Sona Sona (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File travelAccountValidation.png    
Similar issues:
KULRICE-8545Travel Account Maintenance (New) Document: Fiscal Officer Accounts Section Issue
KULRICE-7191No validation on account numbers of Travel Maint document
KULRICE-8038Travel Account Maintenance (New) account number validation broken and validation message nulled
KULRICE-6855Travel Account Maintenance document routes to exception
KULRICE-11814Exception on travel account maintenance document
KULRICE-5477Rice Dev: KRAD Travel Account Maintenance (new) error
KULRICE-13768Create AFT for Travel Account Bulk Update
KULRICE-12852Direct inquiry icon is not appearing for sub account on travel account maintenance document
KULRICE-7848Travel Account Document has a NPE on empty subsidized percent
KULRICE-11548KRAD Sampleapp Demo Travel Account Maintenance New Travel Account Type Code lookup doesn't select checkbox on value return
Rice Module:
KRAD Feature Area:
Application Requirement:
KAI Review Status: Not Required
KTI Review Status: Not Required


On the Travel Account Maintenance Document (New)...

1. The Travel Account number is missing its needed lookup
2. The Account Number and Sub Account number give a must be numeric error, but the delivered account and sub account numbers are all alphanumeric (a1 for example).

Both issues occur on all documents of the Sample Travel App, both KNS and KS L&F, where these fields exist.

Comment by Jerry Neal (Inactive) [ 20/Nov/12 ]

Hey Matt,

Since this is creating a new account record, does it make sense to have a lookup on an existing account? The framework will throw an error if you try to edit an existing account through the new maintenance document.


Comment by Sona Sona (Inactive) [ 04/Dec/12 ]

Hi Matt,
The two columns ACCT_NUM and SUB_ACCT are defined as VARCHAR at the db level. Do we want to change the validation pattern to AlphaNumeric or keep the Numeric validation and change the underlying data? Thanks.

Comment by Matt Sargent [ 04/Dec/12 ]

we should change the validation pattern. thanks!

Comment by Jessica Coltrin (Inactive) [ 08/Jan/13 ]

Since these were fixed on the trunk, they are 2.3.

Generated at Thu Jun 04 06:09:40 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.