Page Comparison

...

 automatically generates an XSD schema representation of your form as you drop controls from the  palette to the form designer canvas. You can download this XSD using the schema button on the XSD by selectingImage Added Download Schema from the Image AddedAction Menu on the Forms and Workflow Homepage. The XSD elements are named after the control names. The types are based on which control you selected from the palette. For example a Quantity control will appear as an xsd:integer. A dropdown will be an xsd:simpleType restriction. Controls with patterns such as the Zip will have an auto-generated type with your pattern. Click "expand Source" for an example.

...

if (form.loadspanish.value == 'yes') {
  SpanishOnly.required = true;
  SpanishOnly.visible = true;
}
else {
  // Must clear values in hidden fields
  // Must be done BEFORE setting <section>.required=false
  name.value = null;
  age.value = null;
  SpanishOnly.required = false;
  SpanishOnly.visible = false;
}

...

When you open (edit) any form/flow workflow that used the schema, the Data Sources area will be refreshed automatically. Do not delete the updated elements from the Data Sources area unless you are absolutely sure no controls in your form were generated from the elements in the previous version of the schema.  '''Also, do not delete the elements and try to re-add them'''. This will cause any controls that relied on the schema to become unbounded and moved out of the schema XML document into the form's default XML document.

...

Let's say you upload a schema with two controls and build a form and a flow workflow with this form as a step 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 Workflow Home page, the form/flow workflow is flagged with an error. When schema update is done, any controls that are no longer valid to that schema are "detached" and fall into the default from scratch schema.  marks them in error (pink background) to give the designer a visual cue that some investigation is necessary.

If you click on the Test icon while the form/flow workflow is in this state, the following error displays:

...

For example, Let's say you create a form and a flow workflow that uses that form as a step from an Address Book schema. The form created from this schema contains Title, Last Name, Address2, Zip code, Home Phone and Gift Idea fields among others. You make these updates to the schema then update it as described above

• Changed the minOccurs value for the Title field to 1 making it required.
• Deleted the Last Name field from the schema
• Moved the Home Phone field into the Address section and removed the Zip Code field from the Address section
• Added a Number of Members in Family field to the schema.

When you edit the form/flow workflow step, after updating the schema, warnings and instructions will show for any controls that have become unbound etc. Notice the Number of Members in Family field has been added to the Data Source and now can be added to the form/flowworkflow.

Although we do not recommend leaving unbounded controls in your form, you are not explicitly prevented from doing so.  If you save your form with unbounded controls, data submitted in these controls will be included in the default XML Submission document for the form itself as opposed to being captured in the XML document for the schema.

...

If you choose to do this, be certain that none of your forms rely on elements from this schema. Any forms that use elements from the deleted elements will be adversely affected, so  will prevent you from deleting any schemas that are currently in use. You will see this message that list all the forms/flows workflows that are using the schema. 

...

If you still need to delete the schema, edit each form/flow workflow listed in the warning message and remove it from the form/flow workflow data source. Then go back to the Schemas tab and delete the schema.

...