Hi George,

Thank you for your questions. As you already found the answer inside the separate topics, objects that are part of Managed Packages are not supported in The Welkin Suite yet.

You can follow the mentioned by you topics. In addition, I'll inform you when this functionality will be implemented to the IDE in the current topic.

Regards,

Kate

Hi Kate,

The link mentioned by Gerorge seems to be broken. Could you please send us the update link to that feature request. This is a really important feature that needs to be in Welkin Suite.

Hi Swagat,

As I've just mentioned in another feature request from you - we are already doing final preparations for the release with managed packages support, so it should be released in the early/mid next week.

Thank you,

Vladimir

So I can se the objects and workflows and everything that is part of the managed package is now being retreived when you ask it to. 

But I can not see the Flows, Workflows created from the Managed Package objects. Why would something as basic as this not be included? 

And why are the managed packages not in-line with the objects, pages etc? And why do ALL the nodes open up - I'm not interested in Classes of Managed Packages, I just want to see the Objects. 

I haven't looked thouroughly but once again Managed Packages is something MavensMate can do well, and is just unsusable in TWS. Whilst I do like that you can exclude some managed packages, when I'm working on an OEM org where EVERYTHING is a manged package, and everything custom is built on top of a managed package, to not see it as part of the main org is such a big let down. 

Hi Jodie,

Than you for your feedback! We appreciate it and it helps us improve the functionality.

As a part of the managed packages support we only download metadata types that are supported by the IDE, so the Process Builder's flows are not downloaded as a part of the managed packages as well.

The logic for storing managed packages items separately from your own items in the project is that the managed packages provide very limited editing capabilities, so most of the included metadatas might be used for reference only. Almost the same applies to sObjects, as you are not able to modify fields that are provided by the managed package itself. This is why we are storing them separately by default. Of course you can drag&drop any items from managed packages to another folders if you plan to interact with them extensively - this is the freedom of customizable project structure, while we define only the initial setup.

Thank you,

Vladimir