writing constraints in one form impacting other forms on other business classes

Legacy Contributor

Hi 

if I write a constraint on a field in one form it seems to make it required on other forms on other screens . For example if I make a field required in AddAddress screen effective date it seems to impact HireResource screen also. How do i ensure that it does not propagate or impact other forms on the same business class or other business class. is there a way to explicitly make a field only required for that particular form and not other screens.

Chad Dirst

It sounds like you have configured the action to make the field required.  This would make the field required for all forms using the field.  

To make the change specific to one form, configure the form in question and add "required".  An example would be:

single column

    Birthdate

        required