...
The Display As property is not available for the following schema controls: Message, Date, Time, Date/Time, T/F.
| Note |
|---|
Although other properties can be changed, in this version of Live Forms, the Display As property will not work if the control is generated from an XSD attribute. A future release will address this issue. |
Required Schema Controls
The required property is disabled for controls from XSD. This is because validation is based on the XSD. Values in the xsd for the required property can be overidden with a business rule.
...
Write a business rule to make the field required.
Let's say a designer created a form from a schema that contained a non-required Text field - minOccurs = 0. The designer adds a Trigger control named tr1 and this simple rule to make the field required when the trigger control is clicked.
Here is the relevant section of the xsd:Section Column width 33% Code Block </xsd:element> <xsd:element minOccurs="0" name="OptionalText" type="xsd:string"> <xsd:annotation> <xsd:appinfo> <frevvo:displaytype>Text</frevvo:displaytype> <frevvo:label>OptionalText</frevvo:label> </xsd:appinfo> </xsd:annotation> </xsd:element>Column width 33% Code Block if(tr1.clicked){ Non_RequiredControl.required = true; }Column width 34% 
- Edit the XSD and update it in the schema's tab for that application.
...
| Warning |
|---|
Update schema will fail if you change the 'global element name' of your schema. You will see this error:
This scenario is not supported by . Changing the global element name changes the schema and cannot be used to replace the previous schema. |
Let's say you upload a schema with two controls and build a form from that schema. Then you modify your schema and delete one of the controls from the xsd. You update the original schema with the modified one. When you go to the Form/Flow Home page, the form/flow may be flagged with an error. When schema update is done, any controls that were that are no longer valid to that schema are "detached" and fall into the default from scratch schema. marks them in error to give the designer a visual cue that some investigation is necessary. The error message will clear if the form/flow is edited then saved even if the designer does not change anything.
If you click the Test icon when the form is in this state, this error message displays.
You will NOT see this behavior if you update a schema for a workflow. This feature is planned for a future release.
Adjusting Your Form after Schema Updates
...