Deleting and renaming SmartObjects and SmartObject properties

When you build a workflow and use SmartObjects in your workflow (such as using references and mapping configuration values to SmartObject properties), the workflow has dependencies on the targeted SmartObject. Your workflow will not deploy successfully if the SmartObject dependencies are missing or not configured. Consider this example: You drag a Send Email step onto the canvas, and use values from a Customer.GetList SmartObject method to populate the email body with values from the SmartObject. The workflow now has a dependency on the Customer SmartObject. If you delete a property from the Customer SmartObject and that property was used in the Send Email step, you workflow will not deploy, since there is now an invalid property mapping in the Send Email step.

To help you identity dependency issues, the workflow designer has a built in Error Console that checks these dependencies as you build your workflow. The error console checks if your configurations are correct. If not, a visual indicator (red exclamation mark or red dot) shows. Open the error console to see a detailed description of the error and use the Show Me... link to navigate to the step where the error exists.

If a SmartObject, SmartObject property or SmartObject method is deleted, renamed or changed, it could affect workflows that depend on that SmartObject. Before you delete or change a SmartObject, research the impact of these changes since the changes could negatively affect workflows that use that SmartObject,. The Error Console is one of the tools you can use to determine breaking changes if you have deleted or changed a SmartObject.

Let's look at a few scenarios for deleting and renaming SmartObjects or SmartObject properties in your workflow.