The Welkin Suite Blog

"Release with fixes" might sound not as cool as a "release with a whole lot of new features", but we are absolutely sure that both types of releases are equally important, so check out the Bloom R27 release with fixes and improvements for some of the important areas of The Welkin Suite IDE. If you're using Salesforce DX, work with Copado directly in the IDE, or work with permission sets and value sets often - this release is for you.

Today we are releasing the first update to The Welkin Suite for Mac in 2019 with a great new feature for those, who work with sObjects and their permissions in Salesforce - Objects Permissions Editor. From now it is one reason less to switch to the Salesforce Setup menu, and one more time-saving scenario in the IDE for both developers and administrators. You will also find some other fixes and improvements in the IDE, so check out this short release notes to find out what's new!

With the ax falling on the Force.com IDE, with its depreciation date set by Salesforce this coming October, I have been getting a lot of questions from our perspective users about why it makes sense to pay for The Welkin Suite when there is the alternative of using Visual Studio Code for free. Also, even a few handful of our current users have asked us what our thoughts are on this, as they just want to maintain their due diligence in making sure they are using the best tool out there for their money. And being honest it is a good question that needs to be answered because as a wise person once said, “if it doesn’t make sense, it doesn’t make dollars.”

So I have tried to put together as many of the answers Vladimir, our head of product, and I have given on this subject into this article to help you out if you have had similar questions running around your head about what is the business case of “Why The Welkin Suite is worth the cost over V.S. Code?”, or “How do I keep justifying spending money for The Welkin Suite when there is the fact V.S. Code is free and has many Salesforce Extensions?”.

After the winter holidays season and a short break, we're finally here with the new release of The Welkin Suite. This time we have focused on the Objects Permissions Editor functionality and some bugfixes. Take a look at what's new in the Bloom R25 and what to expect from us in the next couple months!

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