Schema Mapper Window

Maps SharePoint fields, form fields, web methods, or other input sources to an XML schema.

Navigation

In AgilePoint Envision, open a process template.
Navigate to one of the following stencils:
- SharePoint
- Web Services
Drag one of the following AgileShapes, and drop it on the process model:
- CAML Query
- WSE (Web Service Extension)
- WCF (Windows Communication Foundation)
To view the entire list of properties, in the Design Tasks pane, click Show Properties.
In one of the following fields, click the Ellipses button. The fields that display vary, depending upon the AgsileShape you are using. For example, Configure.
On one of the following windows, under the Output Mapping or Request/Response tab, click the Ellipses button:
Note: If you have changed your XML schema since the last time you opened the Schema Mapper window, when you click the button to open it, you are prompted with the following options:
- Reset All Mappings - Deletes all mappings that have been made in the Schema Mapper for this activity.
- Remove Invalid Mappings only - Deletes only the mappings that are rendered invalid by the schema change. Valid mappings remain the same.
- Cancel - Aborts opening the Schema Mapper window.

Field Definitions

Field Name	Definition
Mapping Schemas for Request/Response and Process Model	Definition: Maps the schemas for a service's request or response and the AgilePoint schema: CAML query schema for a response and AgilePoint schema WSE service schema for a request/response and the AgilePoint schema WCF service schema for a request/response and the AgilePoint schema The source and the destination schemas are displayed in a tree-view structure in the left and right panes. Allowed Values: Read only - However, the drag and drop operations are supported to map the schemas. Drag a data node from the source schema pane to the destination schema pane: Green line - The data type of source and destination nodes matches. Blue line - The data type of source and destination nodes doesn't match. The data conversion is required to map the schemas. Red line - Specifies that the custom data conversion is required.
Automap	Function: Maps all fields in the data source and the process schema that have the same name.
No Data Conversion needed	Definition: Determines whether the data conversion is not required between the source and the destination schema data fields. Allowed Values: Deselected - Data conversion is required between the schema data fields. Selected - Data conversion is not required between the schema data fields. Default Value: None However, the No Data Conversion needed option is selected if the data type of the source and destination schema data fields matches.
Default Data Conversion	Definition: Determines whether the default data conversion is required between the source and the destination schema fields. Allowed Values: Deselected - Default data conversion is not required between the schema data fields. Selected - Default data conversion is required between the schema data fields. Default Value: None However, the Default Data Conversion option is selected if the data type of the source and destination schema fields doesn't match.
Custom Data Conversion	Definition: Determines whether the custom data conversion is required. You can create your own data conversion types by using the Add button. Allowed Values: Deselected - Custom data conversion is not required. Selected - Custom data conversion is required. Default Value: Deselected
Add	Opens the Following Window: Custom Mapping Code Window Purpose of this Window: Specifies custom C# code that can be used to map fields to an XML schema.
Edit	Opens the Following Window: Custom Mapping Code Window Purpose of this Window: Specifies custom C# code that can be used to map fields to an XML schema.
Delete	Function: Deletes the selected custom data conversion from the list.

Common Configuration Tasks

Parent topic: Configuration Windows Parent topic: Common AgileShape Configuration Windows