Workflows on objects from a managed package are ignored

[jeremyross]

Solenopsis seems to ignore workflow on objects from managed packages. Is there a way to force it to pull/push these, as there is with custom objects (sf.members.objects.values property)?

[jeremyross]

I think the same thing applies to other types, such as layouts. E.g., a managed package includes a layout, which can be modified in the installing org, and therefore makes sense to track and deploy.

[pcon]

This is an interesting problem because the ant target with a wildcard for members doesn't pull down anything in a managed package. To get this, we'd have to query the metadataAPI to get a list of objects and then add those individually to the members list in the package.xml prior to pulling. Might be worth seeing if we can do a stopgap of having a list of managed package objects in a text file and having Solenopsis read that (if it exists) and having them added to the package.xml at runtime.

@sfloess What are your thoughts on adding a -Dsf.managedObjectList=/path/to/objects.txt that is in the format of

sf4twitter__Twitter_Account__c
sf4twitter__Twitter_Contributor__c
sf4twitter__Twitter_Conversation__c

And adds a <members>sf4twitter__Twitter_Conversation__c</members> for each entry in that list under objects. I think that will also pull down the layouts and workflows, but I'm not 100% sure. It would be easy enough to add them to the workflows section, but layouts is a bit harder.

[sfloess]

@pcon - yeah sure seem reasonable. I'm realizing I need to get moving on the metadata api ;) But yes seems fair.