Incorrect Mappings

Any incorrect statements are displayed in red in the Function panel.

Errors can occur for a number of reasons. For example,

a required element has no statement, and therefore must be specified
the function’s input schema has changed and existing statements may no longer be valid
the XPath formula for an element may contain an error

You should correct any errors before attempting to test or deploy your process definition.

To help find potential problems in your mappings, click the Mapper Check and Repair button. This button displays a dialog with all potential problems in the specified mappings. You can select the Fix checkbox for potential errors, and TIBCO BusinessEvents will attempt to fix the problem.

Some potential problems in the Mapper Check or Repair dialog cannot be fixed easily, and therefore there is no check box in the Fix column for these items. For example, if an element expects a string and you supply a complex type, the corrective action to fix the problem is not clear, and therefore TIBCO BusinessEvents cannot automatically fix the problem. You must repair these items manually.

XPath 2.0

For XPath 2.0, in addition to the earlier specified errors, you can also see the errors when there is no explicit typecasting of different data types, such as, mapping a boolean value ($processapplication/start) to a input of data type double. In such cases, you can fix the typecasting error in following ways:

Run the Mapper Function Migration wizard to fix the common mapper issues. See Migrating Mapper Functions From XPath 1.0 to XPath 2.0 for more details.
Click the Fix Typecasting Error icon to autofix all typecasting errors.
Open Check and Repair window and select the Fix checkbox for the typecasting error to fix the selected error.
Perform explicit typecasting using the constructor functions, such as, for earlier example use xsd:double($processapplication/start) to explicitly typecast the boolean value to double.