Clayton

Drill down on any issue detected by Clayton and see a code snippet without leaving Clayton. Works for any repository and environment!

___________________________________________________________

Connecting an environment now generates a link you can hand over to any Salesforce administrator, to let them securely connect their org. The link is unique and will be used to prepare a scan report that only you and your team can see. Clayton users can now scan any orgs without knowing the orgs’ admin credentials or having to set up a Salesforce connection beforehand.

New “make suggestions” protection mode

A new <code>Make suggestions</code> protection mode automatically gives advice to developers with possible improvements to pull requests without forcing them to make such changes. Read more <a href="https://help.clayton.io/en/articles/2135883-monitor-your-code-with-automatic-reviews#h_660b6ed29f">here</a>.

More settings to control your environments

Control both <code>Visibility</code> and <code>Team</code> of your Environment to manage confidentiality and who in your workspace can access scan reports for any Salesforce Org.

A new <code>Ignore List</code> tab lets you exclude files and paths you don’t want to scan using regular expressions.

<a href="https://help.clayton.io/en/articles/6394886-database-changes-in-flow-loop-paths">Database changes in Flow loop paths</a>

<a href="https://help.clayton.io/en/articles/6394903-hardcoded-id-flows">Hardcoded ID (flows)</a>

<a href="https://help.clayton.io/en/articles/6394911-missing-fault-path-in-flows">Missing fault path in Flows</a>

<a href="https://help.clayton.io/en/articles/6394916-multiple-record-triggered-flows-on-the-same-object">Multiple record-triggered flows on the same object</a>

<a href="https://help.clayton.io/en/articles/6432858-nulls-empty-checks-after-lookups-in-flows">Nulls/Empty checks after lookups in Flows</a>

<a href="https://help.clayton.io/en/articles/6432870-flows-without-description">Flows without description</a>

<a href="https://help.clayton.io/en/articles/6432885-multiple-automation-on-the-same-object">Multiple automation on the same object</a> (working with Apex Triggers, Flows, Workflows)

- <a href="https://help.clayton.io/en/articles/6394886-database-changes-in-flow-loop-paths">Database changes in Flow loop paths</a>
- <a href="https://help.clayton.io/en/articles/6394903-hardcoded-id-flows">Hardcoded ID (flows)</a>
- <a href="https://help.clayton.io/en/articles/6394911-missing-fault-path-in-flows">Missing fault path in Flows</a>
- <a href="https://help.clayton.io/en/articles/6394916-multiple-record-triggered-flows-on-the-same-object">Multiple record-triggered flows on the same object</a>
- <a href="https://help.clayton.io/en/articles/6432858-nulls-empty-checks-after-lookups-in-flows">Nulls/Empty checks after lookups in Flows</a>
- <a href="https://help.clayton.io/en/articles/6432870-flows-without-description">Flows without description</a>
- <a href="https://help.clayton.io/en/articles/6432885-multiple-automation-on-the-same-object">Multiple automation on the same object</a> (working with Apex Triggers, Flows, Workflows)

<a href="https://help.clayton.io/en/articles/6432863-untested-lightning-web-components">Untested Lightning Web Components</a>

- <a href="https://help.clayton.io/en/articles/6432863-untested-lightning-web-components">Untested Lightning Web Components</a>

<a href="https://help.clayton.io/en/articles/6435858-naming-conventions-on-apex-inner-classes">Naming conventions on Apex inner classes</a>

<a href="https://help.clayton.io/en/articles/6435862-naming-conventions-on-apex-test-classes">Naming conventions on Apex test classes</a>

<a href="https://help.clayton.io/en/articles/6435863-naming-conventions-on-apex-test-inner-classes">Naming conventions on Apex test inner classes</a>

<a href="https://help.clayton.io/en/articles/6435960-naming-conventions-on-sobjects">Naming conventions on sObjects</a>

<a href="https://help.clayton.io/en/articles/6435963-naming-conventions-on-sobjects-fields">Naming conventions on sObjects fields</a>

- <a href="https://help.clayton.io/en/articles/6435858-naming-conventions-on-apex-inner-classes">Naming conventions on Apex inner classes</a>
- <a href="https://help.clayton.io/en/articles/6435862-naming-conventions-on-apex-test-classes">Naming conventions on Apex test classes</a>
- <a href="https://help.clayton.io/en/articles/6435863-naming-conventions-on-apex-test-inner-classes">Naming conventions on Apex test inner classes</a>
- <a href="https://help.clayton.io/en/articles/6435960-naming-conventions-on-sobjects">Naming conventions on sObjects</a>
- <a href="https://help.clayton.io/en/articles/6435963-naming-conventions-on-sobjects-fields">Naming conventions on sObjects fields</a>

<a href="https://help.clayton.io/en/articles/2136074-crud-and-field-level-security">CRUD and Field-Level Security</a>: CRUD/FLS checks now support <i>@InvocableMethod</i>

<a href="https://help.clayton.io/en/articles/2139312-naming-conventions-on-apex-classes">Naming conventions on Apex classes</a>: Improved the rule not to enforce conventions on inner classes (can be covered with <a href="https://help.clayton.io/en/articles/6435863-naming-conventions-on-apex-test-inner-classes">this dedicated rule</a>)

- <a href="https://help.clayton.io/en/articles/2136074-crud-and-field-level-security">CRUD and Field-Level Security</a>: CRUD/FLS checks now support <i>@InvocableMethod</i>
- <a href="https://help.clayton.io/en/articles/2139312-naming-conventions-on-apex-classes">Naming conventions on Apex classes</a>: Improved the rule not to enforce conventions on inner classes (can be covered with <a href="https://help.clayton.io/en/articles/6435863-naming-conventions-on-apex-test-inner-classes">this dedicated rule</a>)

Support for announced Diff improvements change on Bitbucket APIs <a href="https://bitbucket.org/blog/improving-performance-on-complex-diffs" rel="nofollow noopener noreferrer" target="_blank">https://bitbucket.org/blog/improving-performance-on-complex-diffs</a>

Protection modes: added advanced settings now allow whether PR reviews should be updated based on new commits or only when there is a change in the issues detected

- Redesigned team and role management
- Redesigned ignore list
- Archive and delete repositories

Engine Improvements: support for multiple extended Apex interfaces

- Support for announced Diff improvements change on Bitbucket APIs <a href="https://bitbucket.org/blog/improving-performance-on-complex-diffs" rel="nofollow noopener noreferrer" target="_blank">https://bitbucket.org/blog/improving-performance-on-complex-diffs</a>
- Protection modes: added advanced settings now allow whether PR reviews should be updated based on new commits or only when there is a change in the issues detected
- Improved repository settings
  - Redesigned team and role management
  - Redesigned ignore list
  - Archive and delete repositories
- Engine Improvements: support for multiple extended Apex interfaces
- Various security hardening improvements

New features

Issue details and preview

Org setup made easy with shareable links

New “make suggestions” protection mode

More settings to control your environments

New rules

Flows

Lightning Web Components

Apex

Rules improvements

Other improvements