...

As soon as you mark a control required, the empty control displays a yellowish background gradient. Until users populate all required controls with valid data, they will not be able to submit the form because the Submit button will be disabled. 

You can change the color displayed by Required fields by modifying a Style and then applying it to your form/flow. If you prefer an asterisk to designate required fields, enable the Accessibility feature by checking the Accessible property on the form/flow Properties pane. This feature was built to allow visually impaired users to access forms. Enabling this property adds an asterisk (*) for all required fields. If users move ahead from that field without filling it, they will see the error, "You can't leave this empty <control name>".

...

If you click on the Submit button in a form that contains invalid data or required fields that are empty (Submit button greyed out), the message shown below will display. This alert is very helpful to users when trying to determine , invalid controls will be highlighted with an orange border. The designer can use a message control to notify the user that fields need to be filled or data needs to be corrected before the form can be submitted. This can be very helpful to users when trying to determine why a form does not submit.

Image Removed

Unchecking the enable if valid on the submit button of a form will not result in the alert and an invalid form will be submitted. This message can be translated into other languagesRefer to this topic for the details.

Image Added

You cannot mark grouping controls (tabs, panels and repeats) required. A section is one grouping control that does have a Required Property.  If a Section has the required property checked, required controls within it show a yellow background in design and Use mode. If the Section has required unchecked, required controls within it DO NOT show the yellow background color in design and Use mode. The yellow backgound background color appears only when one of the required controls in the section is filled making it mandatory to fill other required controls within the section. 

...

This property is very useful when using rules to hide/show sections depending on something else in the form. If you hide the section you may have to set the required property to false . See Visible/Invisible Sections in Rules Examples for full detail

...

This property determines whether the control is enabled or disabled when users first access your form. If unchecked, users may not enter a value in effectively making the control readonly.  Data cannot be entered until the control is enabled. (You can enable the control using a Rulerule.)

For example, say you are creating a wedding invitation form and want to know if the people completing your form are bringing a guest. Your form might include a text control for the guest’s name that becomes enabled only after users indicate (in another control) that they are in fact coming to the wedding.  

You are not permitted to disable grouping controls such as panels or repeats. However, there is an Enabled property for Sections, each of the columns in a Table and each tab in a Tab control. If "enabled" is set on Tab or Section, controls inside of these group controls would be enabled. Conversely, if the property is unchecked, controls inside of a section or tab would be disabled. This property will make it easier to write Business Rules. Disabled tabs are still selectable and disabled sections can still be expanded and collapsed.

You can enable/disable the selection controls via rules thereby enabling/disabling all the selection control options. It is not possible to enable/disable individual options.

Disabled tabs are still selectable and disabled sections can still be expanded and collapsed. This is as designed. If you are trying to show/hide the contents of a tab/section, use the Visible property. 

...

• Default - The background color for Default depends on the color scheme and is currently a grayish gradient in all color schemes. This is the message type for new controls
• None - has no border, decorator or color. Controls in migrated forms will have this type post migration
• Bordered - a border but no decorator or color.
•  Info Info - default decorator and blue background color.
• Success - default decorator and green background color.
• Warning - default decorator and yellow background color
• Error - default decorator and a red background color. 

...

Another is the showhelp css class that is built into the Tight layout. For example, you can reduce white space even further with the Tight layout so that you have virtually no space between controls by selecting the hide label property on each control. This can be a way to implement a grid type layout as shown in this sample form below. 

When controls are this tight together there is no room to display the help icon for controls with help text. Notice that the first row of controls does displays the help icon. This is done by putting the string showhelp into the css class property for each control in the first row. This is a useful way to have help at the top of each column.

CSS Class to Set Font Size for the Table and Message Controls

...

This CSS class is only available in v6.1.4. You can use the CSS class f-submit-error to display a message control that notifies the users that the form cannot be submitted because there are required controls that are empty or controls that contain invalid data. Refer to this Valid Forms#InvalidFormNotificationforUsers topic for the details.

Image Added

If you are using Live Forms in-house, Cascading Style Sheet code that was used in themes applied to forms/flows in previous Live Forms releases, can be added to a newly created style.css file in the frevvo.war file . The context parameter, frevvo.css.url, in the web.xml file must be changed to point to it

Button Color

You can change the color of the trigger button by selecting a choice from the Button Color dropdown.

...

This property applies only to Submit controls. By default  disables the form's submit button until all required fields are filled and contain valid data. See Valid Forms for details of this feature. However, sometimes you may wish to override ' default behavior and allow the user to submit a form even if it is invalid. To do this, uncheck this property.

If you click on the Submit button in a form that contains invalid data or required fields that are empty (Submit button greyed out), the message shown below will display. This alert ,  the invalid fields will be highlighted with an orange background color. The designer can also display a message instructing the user what to do. This approach is very helpful to users when trying to determine why a form does not submit.  Unchecking this property on the submit button of a form will not result in the alert and an invalid form will be submittedRefer to this topic for the details.

Image Modified

Prefix Property

Custom groups with rules included when dropped back onto the same or another form, will contain a special "Prefix" property. The property will automatically be given a unique value if you drop the group onto the same form 2 or more times. This ensures that the group controls have unique element name. You can view the impact the prefix has on the element names by viewing the form's schema or the control's property panel. Using the prefix property, you can write a separate rule to manipulate the 2nd or greater instance of the custom control. Refer to this documentation for the details.

...

Max Size

The Max Size property is used to set the upper limit for each attachment uploaded using the Upload Control in your forms/flow. It is set to 10Mb in the cloud. In-house customers should refer to the Max Size property for information about configuring this property for an in-house installation.