How the Restart attribute works

The Restart attribute can do the following tasks:

• Identify valid data objects that contain objects in error.
• Tell the system where to start over when a unidentified foreign object (UFO) is encountered in the data during the validation process.

  All unrecognized data is considered to be an error of the type with Restart assigned to it.

• Identify the UFOs and existing data objects in error that are ignored when mapping input to output.

When an invalid data object is a component that does not have the Restart attribute assigned, that component is marked in error. If components from the beginning of the data are marked in error because no Restart attribute is assigned, the following results occur. Processing stops after validation, and input data is not mapped to output.

Do not put the Restart attribute on a required component. There must be a number of valid instances that is enough to cover all of the required components. If you have a required component that is not valid, the Restart attribute does not validate the data.

When the Restart attribute is added to components that have only one mandatory element, it is ignored. Adding Restart to the parent level works only when there are no children that have one mandatory value. In this scenario, the ISERRORS and REJECT functions would report the first error. But if there are other errors, they are not captured because Restart stopped and restarted at the next parent level.

The Restart attribute is supported on components of Xerces schemas.

For more information about using the Restart attribute, see the map designer documentation.