Hi emer.ingeniero,

Thanks for a good word :)

We have very tight plans for 2 next month (polishing eveyrhing to be as good as possible, adding final touches + implementing some cool new features), however we have in mind adding additional metadata components and depending on our velocity we'd try to add them before Dreamforce.

In the meantime it will be helpful if you'll list us what exactly metadatas you'r waiting for so we'll at least try including some of them as soon as possible.

Thanks,

Vladimir

Hi...

First of all I want to say that your VS plugin editor for APEX is awesome. I have extensive experience writing code for the force.com tooling API and it looks like you guys have nail down this connector with VS. I am wondering if it will be possible within your architecture to expose the package that the tooling API uses to retrieve and update metadata objects, that way we can decide which metadata objects from the organization we want to carry over and which ones we don't care. I have a small deployment tool using jsForce that uses that concept and works quite well. It would be interesting if we can carry over that concept to your tool.

Thanks!

Jorge.

Having the custom label metadata i think is simple from your side, and is much usefull for us. Our developpers here create custom labels from the metadata itself rather than from the application, as we often use them in codes, so as we code, we declare then easily as variables, just by creating them from the metadata, without shifting from our IDE to the online salesforce app.

Hi Vanessen,

Yes, you're right - custom labels support is a simple addition and we're going to release this tomorrow (if we won't discover anything during testing).

However this implementation will still miss custom label completion in Apex, but this point is already added to our backlog and will be implemented pretty soon.

Thanks,

Vladimir

Are there any plans to suport Flow and Process Builder Metadata?

Hi Tomic,



Thank you for your question.

The Flow metadata type will be added in a frame of the next extending of supported metadata in The Welkin Suite IDE. This will be implemented in several months.

As for the Process Builder metadata, we are considering adding this as a part of our declarative development support plans.



We will keep you updated on these releases.

Best Regards,

Kate

Flows and Process Builder would be a huge help and add infinite value to a good tool.  It could be great, but right now is missing those core pieces. As we navigate away from building triggers for everything we use more and more flows and process builder.  A bit annoying to be able to deploy/move around PART of a solution but then have to use a different tool to move the remaining parts (flows, process builder).

Hi Shane,

Thank you for your post and for the use-case.

The Flow metadata is already supported in The Welkin Suite for Windows and soon it will be available in TWS for Mac.

As for Process Builder, it is present in our working plans in a frame of declarative development expansion. However, right now I cannot tell when exactly this would be done.

I'll inform you when this functionality will be available for you in The Welkin Suite IDE.

Regards,

Kate

Thank you for the update.  As for the process builder, I am not necessarily looking to be able ot update that metadata but I would like to be able to view it and move it around with the suite.  Pretty much all metadata should be available for that purpose.  That way we don't have to use the suite and then also ANT/Force IDE for a second portion.