If you created a project that uses an XML Schema and the
XML Schema changes, you can attempt to update the existing XML Schema
with the new XML Schema.
Updating to a new XML Schema means that any of the project
entities that interface with the XML Schema might be affected by the
change. The following project entities can be affect by XML Schema
change:
- Maps that refer to the XML Schema, both stand-alone maps and the
inline maps in activities.
- Variables that refer to the XML Schema.
- XPath expressions in orchestrations.
- XPath expressions used in job keys.
- Some Endpoint configurations.
- Conditions defined in orchestrations.
During the update process, Studio reports which project entities
are affected by the change before the change is committed.
For
example, an XML Schema defines an input parameter to the Map
Variables activity. In the From Orchestration pane of
the Map Variables activity there are links
between the nodes of the input parameter to the nodes of the output
parameters. When the XML Schema that defines the input parameter is
updated to the new XML Schema, those links might no longer be valid
if the input nodes have been renamed or removed in the new XML Schema.
You must recreate the links in order for the orchestration to be valid
again.
In some cases, Studio completely prevents the uploading
a new XML Schema for the following reasons:
- The new XML Schema is invalid.
- Uploading the new XML Schema to replace the existing one, would
result in an invalid project.
Note: Updating an existing XML Schema (as described in the
procedure below) is different from loading multiple XML Schemas into
a project by either dragging a file into the Project tab
or right-clicking on the XML Schemas folder in the Project tab
and selecting Add Document. Updating an existing
XML Schema replaces the existing XML Schema in the project while uploading
the same file into the Project tab creates
two instances of the XML Schema in the project.