Symptoms

Smart Object GUID and Migration
 

Diagnoses

It appears that when a Smart Object (SO) is created on our Development server, K2 identifies it with a GUID. This SO can be used inside of K2 Studio to build and run workflows on the Development server. However, when deploying to a Production server, the Workflow will still reference an SO GUID in the Development database, and we get errors in the Workspace, e.g. "Can't find Smart Object ... GUID ..."

So, how do we migrate Smart Objects successfully so we don't have to recreated them in Production (it's a real pain). Can we copy rows of data? Or is there another migration method you recommend and have documented?

 

Resolution

Package and Deployment tool is one of the options that you can use to deploy workflows, forms, SmartObjects, etc from one environment to another.
Another option is to use K2 Studio to deploy your SmartObjects to Production server directly. The GUID will remain the same if you are using same SmartObject that you created and deployed to Dev environment.