Alert field length limitation

Is this a new limitation that was added in the archetypes (see attachment)? Not sure whether or not to report a bug, but this has started happening after upgrade.

I just looked back at 1.6, and it has the same maxLength=15 in the archetype description, so I'm curious why we haven't seen this before. Perhaps it wasn't checking until now?

Is there a particular reason why this would be limited to 15?

Cheers, Paul

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: Alert field length limitation

The archetype has had that restriction since 2006, and I'm not aware of any code changes. Have you used that particular alert type before?

In any case, its an arbitrary restriction, probably selected to enforce a particular layout. You can safely remove it. I've removed it in revision 5598.

Regards,

-Tim

Re: Alert field length limitation

Thanks Tim, Probably will just reduce the length of them for now... hate to have to edit lots of archetypes when upgrading. No issue really though.

Cheers, Paul

Re: Alert field length limitation

Strangely, the system permitted creation of these alerts in the past with strings greater than 15 characters... not sure why. After changing the string length, it's still not permitting creation of the alert using the same one... so the doctor's are asking to create a new alert, and then I may need to go into the DB and manually change the relationships. Not sure exactly how it happened. There must have been some validation that was getting missed that's now come on-line for the max length?

-Paul

(attached screenshot showing this have been created)

AttachmentSize
screenshot.png 118.61 KB

Re: Alert field length limitation

Note that its the lookup.patientAlertType code that is exceeding the field length restriction. This is derived from the alert type name when it is saved for the first time.

The simplest approach is to:

1. edit act.patientAlert in Administration|Archetypes

2. select the alertType node

3. change the Max Length to 30, or something larger than the longest lookup.patientAlertType code that doesn't cause the display to look odd

4. save

In 1.7, the restriction is removed, and the display doesn't use the Max Length to determine the field width.

Re: Alert field length limitation

Yep... I've done exactly that. Thanks!

-Paul

Syndicate content