The Welkin Suite Blog

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? 

A promising title, isn't it? Believe me or not, but the upcoming release itself is even more promising! So let me tell you what's going on, we've heard a lot of feedback from different sources related to the way of how The Welkin Suite works with Salesforce organizations, and thank you for that. And in those feedbacks, we have heard some very helpful critics that were mostly related to the following aspects:

• A lack of support for the %Put_Your_Metadata_Name_Here% metadata type
• A rock-solid connection of a project tothe organization, without any option to easily switch between orgs with the same sources
• Unbeatable safeguards that prevent you from overwriting something in Salesforce
• A lack of a way to work with plain "src" folder in the IDE

You know what? All of this (and even more) will be resolved in the next 2 weeks, and in this post, we will highlight to you some of the details with very early screenshots.

It is time to welcome one more big "cumulative" update of The Welkin Suite for Mac - yes, today we are rolling out great new version of the IDE with some really important and helpful changes. It is even hard to say if the focus is on point-n-click Salesforce development, taking into account a set of new features for sObjects Inspector and absolutely awesome Field Usage Report, or if it is geared towards those who write code with Custom Metadata support and Find Usages for Apex.

But who really cares about defining a "theme" for the new version of the IDE if there are so many great features? Btw, 5 minutes of your time spent on reading release these notes will make your life much easier right from the first launch of the Blaze R12 as you'll know where to look for all the new features (and you are going to want to look for them )!

We hope you've missed us over these past weeks, and we hope that you'll like what you will see in The Welkin Suite Bloom R18. We have started working on a very big update to the IDE that will bring you all metadata types and will change a lot of things of how we interact with Salesforce, but yes - started, but not yet finished 

However, we have a bunch of great updates today - starting from 5 features & improvements for the built-in sObjects Inspector and upto the Custom Metadata support and 'Find Usages' functionality in Apex.

Phew... Finally the Bloom R17 version of The Welkin Suite is ready to roll-out to you, so you'll enjoy then new great features we were working so hard last month! First of all it is the easiest way to analyze your Apex code against 180+ rules using the CodeScan tool - couple clicks and here's your comprehensive report on code quality! Won't say 'second', so next to CodeScan we are introducing you a great Field Usage Report that will help you finding out where and how your field is used and what might be the impact of any changes in it - without digging into XML files!

The built-in Task List panel will help you organizing your tasks, improved fields editor in sObjects Inspector will save your time when working with your sObjects and a bunch of other handy changes. Read more on what you'll find in the Bloom R17.