Execution from forms

This action runs the triIntegration - Execute workflow. The integration object record becomes read only and its status changes to Processing. When the integration processing is completed with no errors, the integration object record changes back to the Ready state. If an error occurred during processing, the status changes to Failed, and the record does not change its state. You must then manually inspect the errors that occurred. However, you can override the inspection and change the record back to the Ready state by clicking the Complete action.

The Execute History section contains records with the details about each integration run. Each detail record contains the status, processing counts, and duration of the run. When an integration run has errors, it also includes a log of the errors and a query section that lists the individual records that failed. When the integration run is triggered from another workflow, the integration object record that contains the full overview of errors also contains a truncated message. The truncated message is in a hidden text field that can be displayed, for example, in an Attention message.

Outbound integrations that export results to an XML format or JSON format can process a maximum of 999 records at one time. If more than 999 records must be exported, you can select the Exceed 999 Result Limit and Return Maximum? option to export all of the results. Because more memory will be used as the result set gets larger, system performance should be considered when selecting this option with larger result sets. For other ways to exceed the 999 result limit, see the topic "Example: Execution from custom tasks" to create workflow logic that can run your integration until all of the records are processed.