Statements, Hints, and Errors
When you display the Input tab for an activity, the existing statements are examined, and any input elements that do not have a statement are displayed as hints. Hints are reminders that you can specify a statement for the input element, but they are not stored as part of the XSLT template for the activity’s input. Hints are displayed in italics with a light blue background. Once you specify a mapping or a formula for a hint, the input element becomes a statement. You can also drag the hint to the left past the dividing line between the panels and the hint becomes a blank statement.
Once you specify a statement in the Activity Input panel and apply the change to the activity, it becomes part of the XSLT template used to create the activity’s input data. These statements are saved as part of the activity in the repository. Statements are only deleted if you manually delete them using the delete button, or if you use the Mapper Check and Repair button to automatically fix errors. Therefore, if the input schema for the activity changes, your statements may no longer be valid. For more information about using the Mapper Check and Repair button to fix statements in the activity’s input, see Repairing Incorrect Mappings.
Any statement or hint that has an error is displayed in red. A hint is only displayed in red if it is a required input element. All required input elements must have statements specified. If a statement is red, you must fix the error before executing this process definition. The Mapper Check and Repair button can help you automatically fix some errors. For more information about fixing errors, see Repairing Incorrect Mappings.