Changes to a simple type definition affect the elements and attributes for which the simple type is the defined type. For example, if the attribute partNum is defined to be of type SKU, changes to the SKU simple type definition affect the partNum attribute.

Changes to a global simple type definition in an IS schema do not affect simple types derived from the global simple type; that is, the changes are not propagated to the derived types in the IS schema.

Simple types in an IS schema can be used as content constraints for fields in pipeline validation. Consequently, changes to a simple type also affect every field to which the simple type is applied as a content constraint.

Changes to a simple type definition are saved in the IS schema. If you regenerate the IS schema from the XML schema definition, your changes will be overwritten.

When you edit the constraining facets applied to a simple type definition, you can only make the constraining facet values more restrictive. The constraining facets cannot become less restrictive.

If you want to edit complex type definitions, attribute declarations, element declarations, or the structure of the schema, you need to edit the XML schema and then regenerate the IS schema.

For an IS schema from a source file such as an XML schema definition or a WSDL document Designer displays the location of the source file in the Source URI property. Designer also sets the Linked to source property to true which prevents any editing of the simple type definitions in the IS schema. To edit the simple type definitions, you first need to make the IS schema editable by breaking the link to the source. For information about allowing editing of elements derived from a source, see Allowing Editing of Derived Elements. However, Software AG does not recommend editing the contents of IS schemas created from WSDL documents.

For more information about constraining facets, see the W3C specification XML Schema Part 2: Datatypes.