Transcript
As we know, the GearSet and Clayton integration enables admins and developers to ship high quality, bug free, and secure code at speed, and we've seen how this fits into GearSet pipelines.
Today, I wanna take this one step further and look at some of the additional capabilities available within Clayton.
So you'll see here on the dashboard, this gives us a bird's eye view of the code health of your application according to Salesforce's well architected framework.
This is looking at over two hundred metadata types covering all aspects of declarative and configuration changes from Apex classes to LWCs and Visualforce pages to flows.
And as you'll see, this can be configured on either a Git repository or directly on a Salesforce org.
We get to see a score as well as a TechNet ratio and how many issues Clayton has detected based on the severity levels that we've configured.
Below, for each core area that I have configured, Clayton will show us all anti patterns and vulnerabilities that fit into that policy type.
And for each rule, what we can see specifically is exactly a summary of the issue that's that's been detected. Here is an example of a risk of exposing potentially sensitive data with an incorrect sharing clause, who introduced the issue, how long it would take to fix, but also a code snippet of where this has been detected.
And, of course, there could be many of these, but with BAU processes, it may be really hard to get even relatively simple fixes prioritized.
So Clayton also has an auto fix capability, enabling you to remediate this en masse.
And this will use either generative AI or prebuilt fixes to suggest resolutions to these vulnerabilities, which we can merge via a pull request as we saw in the video shown with pipelines in Clayton integrated.
Additionally, scans can also be run on specific branches.
So here we can see the scan that was run on the main branch, but I could look at any of my other branches as well.
Every team has different expectations when it comes to the coding standards and workflows that they require.
So with policies, you can manage your coding standards all in one place. And by enabling one or more policies, all of which are underpinned by multiple rules, When these are applied on your projects, Klagen will make sure all of your developments comply with your requirements, and these rules will allow you for test to test for over a hundred Salesforce best practices curated and updated with every Salesforce release. As we mentioned earlier, these are all built around that Salesforce well architected framework.
Additional configuration is also available, for example, to control when developers stumble across a bad piece of code, should they fix it straight away or take a note for later? And whichever your preference, Clayton will ensure your team behaves consistently, and that is done with protection modes that provide flexibility over that behavior based on these four options, going from left to right in terms of severity.
On the left hand side then, let's have a look at the insights that Clayton also provides.
So for dev team leads or administrators, insights provide helpful metrics about your Salesforce engineering, including how code quality is improving over time, your security exposure to the OWASP top ten vulnerabilities, and how each of your team are contributing to your code base.
Within each of these team members, we could also see suggestions to support your team grow and develop over time, as well as suggested trailheads to look at.
And, of course, there's a whole suite of other capabilities here, which we'll look at another time. But, hopefully, this just gives you a quick flavor of some of the additional capabilities within Clayton.
As always, if you have any other questions, thoughts, or concerns, please just get in touch.
Thanks, everyone.
