Symptoms

Issues:
1. Manually adding a property to a SmartObject generated off of a SharePoint list results in weird behavior. It will only be visible from an item or list view is created with said SmartObject and not forms, other views, or the context browser. It also may not store values correctly or at all.
2. Conditional rule “if a control contains a specific value” actually checks if a control’s value is equal to a specific value, not if it contains a specific substring. This wording is misleading.
3. “Save as Workflow template” is greyed out and unusable despite being in the Appit documentation.
 

Diagnoses

Appit
 

Resolution

Workarounds:
1. Add a hidden SharePoint list column and then regenerating the SmartObject. This is counterproductive if you don’t want your SharePoint list filled with unused columns.
2. Add a conditional statement “if an advanced condition is true” and use the ‘contains’ method within that.
3. Save as a WKPRX file, open the file in the Designer workflow editor, change the name, then save. Item references will likely become unsynchronized and need to be re-dragged from the context browser.