On this forum you can see a list of new features requested by users and you can also cast your own vote (you need to login to vote).
#44490 by bkonia
Tue Aug 22, 2017 8:22 am
If you set an attribute to Required, that attribute will be unconditionally required in all forms, regardless of whether or not the field is visible and even if the field does not even appear on the form. This is the correct behavior, since the attribute is a property of its parent object, not a property of the form.

However, there are many times when we need to make fields required on certain forms, without making them required in the underlying attribute. For example, I have a form that's a loan application. The form always has a primary applicant, for which all attributes are required. The form also contains a toggle switch to enable a field group for a co-applicant. If it's enabled, the co-applicant fields should be required. Otherwise, they should NOT be required.

Therefore, I'm requesting the following:

1. The ability to make a form field required, even if the underlying attribute is NOT required.

2. In instances where the attribute is NOT required and the form field IS required, the validation should only take effect when the form field is visible. So, for instance, if you hide a field group by adding a condition to the "Not present when" property, validation would be disabled for fields marked Required at the form level. Likewise, if you hide a required field using READ PROTECT, that field would no longer be required.

I know you can accomplish this using rules, but REPORT ERROR displays ugly dialogs, not elegant inline client-side validation messages. This makes for an inconsistent and amateurish-looking UI experience. In the example I mentioned, the primary applicant fields would display client-side validation messages, while the co-applicant fields would display the validation messages in popup dialogs.

Another approach would be for Aware IM to provide an action like VALIDATION ERROR, which would cancel the form submission and display an inline validation error at the specified field. For example:

If MyObject.MyAttribute = '' Then
VALIDATION ERROR 'You must enter a value for MyAttribute' MyAttribute

The advantage of this approach is it would provide total flexibility to customize your validation messages in terms of their content, location and conditions.
#44498 by tford
Tue Aug 22, 2017 2:58 pm
I agree with Brad that improvements in this area would add to our flexibility.
#45006 by PointsWell
Thu Sep 28, 2017 3:50 am
I would also greatly like the ability to apply a business rule to an attribute

Such as:
Code: Select allIF BO.Attrib1='Yes' THEN BO.Attrib2 IS MANDATORY

and have the red flag appear on the UI.
#45129 by BenHayat
Sun Oct 08, 2017 1:25 pm
I've requested for this feature directly from support several years ago, as it's something I've used in other tools for years by making "required" fields on forms than at object level.

I hope support would implement this, as it is used widely in many business forms.

Who is online

Users browsing this forum: No registered users and 1 guest