Skip to main content
All CollectionsRelease Notes
Release 24.10.01--New component, Hide New Deployments button, Outgoing Webhook, Pull request validation CI Jobs
Release 24.10.01--New component, Hide New Deployments button, Outgoing Webhook, Pull request validation CI Jobs

CustomFeedFilter, Restrict direct deployments, Action condition and issue key replacement in outgoing webhooks, Pull request validation

Do Quoc Dat avatar
Written by Do Quoc Dat
Updated over 2 months ago

CustomFeedFilter Metadata Support

We’ve added support for CustomFeedFilter metadata (see the component selection grid in the screenshot below). Search for the Component Type "Feed Filter".

Hide New Deployments button in the Deployments tab (screen)

  • This new feature allows a Team Owner to hide the New Deployments button so that team members must use Work Items instead of Deployments. Team Owners can configure this global setting in Account Settings > Team and Licenses tab.

Action Condition and Issue Key Replacement in Outgoing Webhooks

  • We've added support for action and status conditions in outgoing webhooks. You can now specify actions such as Deploy or Validate, with action statuses being either Succeeded or Failed.

  • Additionally, issue IDs will automatically be replaced in the webhook URL by using the placeholder $ISSUE_TRACKING_ID.

Example:


If the issue ID in your deployment is CRM-1231 and your webhook URL is configured as https://sample.com/rest/api/2/issue/$ISSUE_TRACKING_ID/comment

Then, the outgoing webhook will transform this URL to https://sample.com/rest/api/2/issue/CRM-1231/comment when triggered.

Pull Request Validation for CI Jobs (Beta)

  • The Validate Pull Request action has been added to CI jobs. Now, whenever a pull request is created or updated, it will trigger a CI job that validates the PR changes against the target Salesforce org.

  • The result of the CI job will be displayed after validation.

Note:

  • This feature is currently provides support for Bitbucket and must be enabled upon team request. Please contact our support team to activate it.

  • Additionally, "PR Created" and "PR Updated" events must be added to the Git webhook triggers. Here’s an example for Bitbucket integration.

Did this answer your question?