Custom API Response Status Code Support

You can now configure custom APIs to return specific HTTP status codes and error messages using the new BaseResponse type. This enhancement allows your custom code to define response details such as 400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, and 500 Internal Server Error. The system reads these values from your custom code and includes them in the final API response, giving you greater flexibility and control over error handling. For more information, see the Define Custom API Response Status Codes topic.

Send Email API: Support for EmailProfile in EmailFromOption

The Send Email API now supports using the EmailProfile object in the EmailFromOption parameter. You can create and manage Email Profiles with full CRUD operations, set the EmailFromOption to ProfileName, and pass the EmailProfileName as a parameter. This allows you to send emails using the address specified at the email profile level, making it easier to standardize and manage email sending configurations across your organization. For more information, see Email APIs.

Custom Error Activity Window Level Error Field Formula Restriction

Hide formulas dependent on Context Record from the Window level error field intellisense dropdown in Custom Error Activity for both Before Save and Callback Workflows.

Enhancement to Custom Dashboard Creation

When you create a new custom dashboard, the system now automatically adds the Custom tag, enables the Enable Embedding option by default, and creates a default URL slug. These enhancements simplify the setup process and help you get your dashboard up and running with minimal effort. For more information, see Creating Custom Dashboards.

Intellisense Support for Identifier and Reference Fields

In the Create Record and Update Record workflow activities, Intellisense suggestions for Lookup and Owner fields now include Identifier and Reference data type fields from the context record. This enhancement allows you to link related records directly within workflows, enabling smoother record cross-referencing during workflow execution. For example, you can automatically create a new Agreement record and link it to its parent Account record whenever specific trigger conditions are met. For more information, see the Create Records and Update Records activity topics.

Workflow: New Activities for API Integration and Data Handling

Introduced two new activities to enhance API connectivity and data processing in workflows:

• HTTP Callout V2 Activity: Connects with external APIs using BasicAuth or OAuth2 authentication. This version improves response handling, supports data transformation, and strengthens integration capabilities. (The existing HTTP Callout Activity will be deprecated in a future release.)
• Data Transformation Activity: Reshapes JSON outputs for downstream workflow steps. You can extract fields, apply expressions, handle collections with index-based access, and generate custom JSON structures with built-in expression validation.

For more information, see the HTTP Callout V2 and Data Transformation topics.

New Translation Management Module

Introduced the Translation Management module to simplify how you manage multilingual content across the platform. This new capability provides automation, flexibility, and centralized control?helping you deliver a consistent experience to global teams.

Key benefits include:

• Automated Translations – When you enable a new language, the system automatically generates translations for menus, fields, and labels in the background, reducing setup effort and speeding up deployment.
• Centralized Language Control – Easily manage active languages for your organization and set a primary fallback language to ensure consistency across all users.
• Custom Translations – Tailor translations to match your organization’s terminology and specific requirements by adding or editing translations as needed.

This new module simplifies language management, helps you scale globally, and ensures accurate, consistent translations throughout the platform. For more information, see Translation Management.

Workflow: Activity Execution Limits and Enhanced Loop Detection

The system now uses enhanced loop detection to prevent activities from running indefinitely. It runs an activity three times, applies a five-second cooldown if it detects a loop, and then runs the activity three more times. If the loop continues, the system halts the activity. The legacy loop detection (up to two thousand executions) still applies for Loop, Fork, and Decision activities. For more information, see the Activity Execution Limits and Loop Detection.