The Welkin Suite Blog

Dear Salesforce community and The Welkin Suite users, 

While everyone is busy with this Holidays season, The Welkin Suite team is working hard on implementing one more very cool feature in the Salesforce configuration area. The one that will nicely extend the Field Level Security configuration options, and fulfill a lot of requests that we've received from you - Objects Permissions Editor. Let's take a quick look at what expects us in the first release of the new 2019 year when this feature will be ready to see the world 

We see the Salesforce platform constantly evolving, and along with that, we see the development processes transforming as well. But do we only see this evolution around those what I would call buzzwords of Salesforce, like moving from Visualforce to Lightning, Salesforce DX, or even about the progression away from having to use code at all? I would say no, and I think a great example of this is how the development and development flows have matured around Apex. Just 5 years ago using GIT with Apex projects was a very scare world in Salesforce, and now it is not scary at all as the tools, developers, and workflows have grown.

So let’s talk today a bit about the different options you and your team have in The Welkin Suite to store your sources and metadata in Git. I am not going to mention anything about flows and best practices, as each project and team is unique in its way of using Git, so we’ll just highlight what you can do in the IDE to make your Git journey easier and more comfortable.

It probably can't be argued that many of us through-out the world appreciate it when companies jump onto the spirt of what has become "Black Friday" and "Cyber Monday", as this gives many of us the opportunity to finally justify purchasing some great stuff, which can make our live more enjoyable, and at prices that fit our end of the year budgets.

We believe you liked our Bloom R19 version of The Welkin Suite IDE and you already have had an opportunity to try those incredible features which were needed  So we are ready to continue to implement more of your requests and, of course, to fix some issues that you have reported to us. This time we paid our attention mostly to Anonymous Apex and SOQL, but not only to this! So in this release for the Windows TWS version, you will find more than 20 different improvements and fixes all over the application.

The Welkin Suite Blaze R13 version is dedicated to covering all of the known issues and imperfections in the teamwork organization for non-SalesforceDX projects, and much of this is based on a lot of feedback from our community- thank you to all that sent ideas and pain points!

It is a huge challenge to highlight anything that was introduced in this release as somehow more important than anything else, as all of these changes were requested and are quite honestly required for a comfortable work with Salesforce projects in complex environments. So due to the significant amount of changes that we made, we'll just list them off without any additional description - so you can find what would be the interesting areas to you and then you can read about them in more detail below.

So the main changes in the new version of the IDE are (the links will lead you to the correct section in the article):

• More than 100 metadata types are added to the list of supported metadata types
• Added a new cool approach to work with such a large amount of metadata types - metadata working set
• Introduced the freedom to reconnect your Salesforce project to any organization in seconds
• Added an option to create (and maintain) TWS projects directly from sources (e.g. from your Git repository)
• Significantly reworked our deployment functionality
• Introduced the deploy-on-save option
• Significantly reworked our pull functionality

The Welkin Suite Bloom R19 version is dedicated to covering all of the known issues and imperfections in the teamwork organization for non-SalesforceDX projects, and much of this is based on a lot of feedback from our community- thank you to all that sent ideas and pain points!

It is a huge challenge to highlight anything that was introduced in this release as somehow more important than anything else, as all of these changes were requested and are quite honestly required for a comfortable work with Salesforce projects in complex environments. So due to the significant amount of changes that we made, we'll just list them off without any additional description - so you can find what would be the interesting areas to you and then you can read about them in more detail below.

So the main changes in the new version of the IDE are (the links will lead you to the correct section in the article):

• More than 100 metadata types are added to the list of supported metadata types
• Added a new cool approach to work with such a large amount of metadata types - metadata working set
• Introduced the freedom to reconnect your Salesforce project to any organization in seconds
• Added an option to create (and maintain) TWS projects directly from sources (e.g. from your Git repository)
• Significantly reworked our deployment functionality
• Introduced the deploy-on-save option
• Significantly reworked our pull functionality

Have you thought what it would be like to have all the metadata from your org in your The Welkin Suite project, but still be able to work with the ones that you most commonly use in the fastest possible way? 

Or, have you ever wanted to feed your Git repo or plain sources directly to TWS, to have a more seamless workflow?

Or, maybe, you were missing some deploy or retrieve options in the IDE?

All of these and even more The Welkin Suite new features will be shown in details during our Release Highlights Webinar on July 26th - sign-up for it and be prepared to this game-changing release of The Welkin Suite IDE!

Ok, we have to admit that at the time of our writing this, we haven't yet released The Welkin Suite Bloom R19, but we'd still like to share with you some of the new great additions that it will introduce so that you will be up to speed by the release. So with that comment out of the way, one of the most very common questions we have had over the past years has been "How to work with my sources that are in Git in The Welkin Suite?" - today we're going to be answering this question.

The Welkin Suite is about to roll out a great release, and I would like to highlight that it’s totally based on your feedback and requests! Some of you may have already seen our announcement on this release of The Welkin Suite but if you missed it - you can check it out here.

This version of the IDE is really full of significant changes for different parts of the IDE's functionality. And now, I would like to clarify some more details to warm up your interest! :) So what makes this version so important?