Hello everyone,
I can't get a "Message Form" to block a DriveWorks form by driving the "Error Result" property on a combo box. The property rule works fine, but no message appears in the form when a specification is executed. I'm looking to display a message if my drop-down returns a null value.
However, I can very well set up this feature on a Text Box...
Has anyone ever encountered the problem or managed to correctly set up a Combo Box to block a form?
Thank you for your feedback.
JFB
Hello!
To tell the truth I have never been too successful in making them work, I have never tried to make them work either for a very simple reason, these error messages appear in the "Task List" at the bottom of your projects If you activate them and they are visible ...
Given the beauty of the interface, they ... Here!
To counter this phenomenon, do not hesitate to:
Place a label next to your combo-box
=> Text :if(IsEmpty(MyListReturn), "My List Returns NOTHING!! ERROR", "")
Packaging labels, your forms and a little bit of your entire form will allow you to better interface your projects,
Without further details, I'll stay on the basics of how this property works:
The error result property has two functions.
In any case, if the result of this rule is empty, there is no problem and no message appears in the "Task List".
The first operation, which is quite obvious, is the one you seem to have used for your TextBoxes. If the result of the error result rule is text, it is used as a message in the Task List to report the "problem".
The second is more often misunderstood. If the result of the error result rule is a number, then the error result refers to a predefined message in the " Form Messages " rules.
These rules are in Stage 2: User Interface/ Form Messages.
Because of this peculiarity, if the result of the rule is zero, it will behave as if it were empty.
So when you mention a null value, whether it's a zero or an empty value, it could explain the absence of a message.
I can see yet another possibility that could explain the absence of a message.
If the drop-down list is in a different Form than the one currently displayed (multiple Forms).
It is then possible to display the drop-down list using a Frame control pointing to the Form Control where the list is located.
In this particular case, the messages generated by the controls seen "through" a form control are currently* not visible when the specification is executed.
* this is the case up to V17. Enhancement requests have already been sent to the publisher to remove this limitation.
If these explanations are not enough to find a solution, I have opened a support ticket in parallel to deal with this issue.
However, don't hesitate to post the final answer in the forum for everyone to benefit from:)
Thank you for your answers,
Indeed, as Mr. DEMUYNCK explains, the "Error Result" property of a control cannot (for the moment at least) be seen and function from a "main" form if the control is on a "secondary" form displayed via a "Frame Control".
Which is my case now.
If I move my "Combo Box" to my "main" form, it works fine, if I put it back on my "secondary" form, it doesn't work anymore.
I'm thinking of overcoming this by putting rules on conditions in the transitions of the "Specification Flow" to block certain buttons or not depending on the values returned from my controls or variables.
Kind regards.
J.F.B.