Troubleshooting custom steps

This topic describes some common issues and troubleshooting steps when working with Custom Steps.

Issues when designing a workflow

Issue: When you configure the custom step in your workflow and select a connection in the list, you may see this error message:
Either a SmartObject was not found or multiple, matching SmartObjects were found.
This error means that the system cannot find a unique SmartObject, with the specific method specified when creating the custom step, generated from the specified service object and service method.
Resolution: To help you solve this, run the Get SmartObject Name and the List Matches methods of the Configuration SmartObject found in the System > Management > Workflows > Custom Step > SmartObjects category. What the methods return gives more details about why these validation messages are appearing. Note that these methods are not available on the custom step management form. Open the custom step management form and click the Update tab. Make sure you selected the correct system name for the service object and service object method.

Issue: You cannot configure the input/output properties or parameters for the custom step.
Resolution: Most likely, there is no SmartObject that uses the Service Object Method you selected when configuring the custom step. Make sure you selected the correct Service Object and Service Object Method, and that a SmartObject exists that uses that Service Object method. You may need to use the K2 Management site to auto-generate a SmartObject for the Service Instance, as shown below: