Initial Value for Plain Text attribute not checked on lengt

Gert

Initial Value for a Plain Text attribute not checked on length,
can this simple test be done at build time?

tford

I don't understand the question.

Gert

tford wrote
I don't understand the question.

A word as 'P a r a m e r a t o r' as initial value for a Plain Text attribute of course does't fit in the default 20 characters. I suppose this error can be detected as soon as the value is entered?

technopak

Hi,

My experience with this is that you should create object rules to manage data entry on forms. The default validation by the system doesn't show an error till the 'Create' button is pressed. The user then receives a system error which refers to your BO attribute name (usually meaning nothing to the use), and when the user clicks 'ok' to that message, the create process cancels completely - not returning to the completed entry form, but returning to the main screen.

That kind of user error trapping/input validation is of very little use. I suggest you use multiple 'Report Error' rules to handle your validation.

Peter

Gert

That's right.

But I mean a test during configuration. Allowing a initialisation string that does not fit in the textfield is allowing an hard-wired error that occurs during operation, while it seems quite simple to prevent it.

Certainly because the rest of Aware IM gives the impression that it is better in delivering errorfree systems than an avarage compiled language.

technopak

The ability to set an initial value into an attribute which is by definition not permitted because of the defined length of the attribute is illogical.

It something I'm sure support need to look at.

Better handling of invalid form field entries would also be a huge help.

Because of the poor error handling at present and the consequent need to validate everything by rules, there is little point in setting any attribute definitions in BOs - unless you simply don't want a user to create such entry and don't care for the frustrations of users who have to commence form filling from the beginning all over again when the system dumps their earlier work.

I agree, these aspects of Aware are much poorer than the vast majority of other features in what is an excellent piece of software.

technopak

Hi Support,

Is it my imagination or have you improved the error handling of invalid entry of attribute values in forms in the latest build ?

For example, when I enter data in my attribute fields which exceeds the permitted length, the system no longer gives an error message and then cancels the running process. Instead it gives an error message and returns the user to the completed data entry form.

Is this something new, it's the first build where I have enjoyed such elegant handling of invalid field input ?

It's great !!

Now if only we could configure the error report to include the presentation label of the attribute rather than the attribute name ............

Is it possible ?

Peter

technopak

Might the configuration of the error message be possible via a locale ?

I notice the error message is 'Value of {0} is invalid or not provided'. Presumably the {0} refers to the attribute (name). Is there an equivalent variable identifier for the presentation label maybe ?

Ever hopeful,

Peter

BobK

How about allowing the editing of auto-generated rules?

aware_support

Seems like the problem of being able to control the error message is relevant to many. We'll try to do something for the next build.

ab042

THANK YOU !! 🙂

technopak

Thank you too 🙂

aware_support

The checking of length has been fixed in build 1238. Other improvements are still to come.

aware_support

Build 1246 allows specifying error messages for the attribute.