Using REPORT ERROR closes form when encountered on CREATE

kklosson

Anyone can try this. Use a rule in the business object that validates something like:

IF Object.Attribute IS UNDEFINED REPORT ERROR 'Attribute is required.'

When this rule is encountered during Create object, it closes the form. Didn't used to be this way in V6.

customaware

Kingsley,

I cant test that at the moment but would adding NO RULES at the end of the CREATE resolve the issue?

kklosson

No because create is when the rule is needed the most.

customaware

I would have thought that Rule would only want to be executed if the User is entering a new instance of the BO Kinglsey.

But in your case you are CREATEing in a process which will not like being interrupted to report the Error.

Can you do the test as a Condition on the Process first?

kklosson

It's simple. The rule checks some condition before the record is committed. If the condition is encountered on CREATE, I can see the form closing while the browser is presenting the error message. If the condition is encountered on EDIT, it presents the message and returns the user to the form as it should. I don't believe the form is behaving properly.

kklosson

Okay folks, here is the problem in technicolor.

http://www.esdevllc.com/videos/Display%20Error%20Error.mp4

aware_support

This will be fixed in the next build. The problem only affects Add New Reference operation with the default implementation.

aware_support

This should be fixed in build 2175