Copyright © Cloud Software Group, Inc. All Rights Reserved

Troubleshooting Graft Steps

There are a number of ways you can troubleshoot errors with graft steps:

•	Set up and inspect the graft step return status codes - see Return Status Codes.

•	Define how the process will stop if the graft step fails - Stopping the Process if an Error Occurs.

Return Status Codes

You can use the following return status code array field values to help troubleshoot problems with graft steps. If you set up a return status, numeric array field, you can capture a status code to help troubleshoot problems. The return codes you can get are:

Return Status	Description
SW_NA	The starting of the sub-procedure case has not been attempted.
1	The sub-case has been grafted and started successfully.
2	The sub-case has completed successfully.
-1	There was an error starting the sub-case: Invalid sub-procedure name.
-2	There was an error starting the sub-case: call step and sub-procedure use different parameter templates.
-3	N/A (only applies to dynamic sub-procedure call steps.)

Stopping the Process if an Error Occurs

The graft step call definition provides parameters that you can use to stop a case of your process (at the graft step) if a specific error occurs. If these are not selected, the sub-cases and process will continue but you may have errors in the case data. On the Graft Step dialog, click the Error Handling tab and choose one or more of the following:

•	Sub-procedure names are invalid

Select this option to stop the process if iProcess cannot find one of the sub-procedures it needs to call.

•	Sub-procedures that do not use the same sub-procedure parameter template.

Select this option to stop the process if iProcess finds parameters that are not in the sub-procedure parameter template being used by the graft step.

•	Sub-procedures that use different versions of the same sub-procedure parameter template.

Select this option to stop the process if iProcess finds some parameters that are not valid for the version of the template being used for this call.

See “Using Version Control” in the TIBCO iProcess Modeler - Procedure Management guide for more information about versions of procedures and templates.

Copyright © Cloud Software Group, Inc. All Rights Reserved