> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://help.sigmacomputing.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://help.sigmacomputing.com/_mcp/server.

# What's new in Sigma

> Sigma release notes for Feb 14, 2025: Expanded options for the Add workbook schedule endpoint, new outbound events in embeds, and more.

## API

### Expanded options for the **Add workbook schedule** endpoint

The [Add workbook schedule](/reference/post-workbook-schedule) endpoint (`POST /v2/workbooks/{workbookId}/schedules`) now supports options that were previously available only from the UI, such as creating a conditional export, repeating pivot header labels, compressing attachments to a zip file, and specifying control values for the export.

## Embeds

### New outbound events in embeds

Use two new outbound events, [`workbook:bookmark:ondelete`](https://help.sigmacomputing.com/docs/inbound-and-outbound-events-in-embeds#workbookbookmarkondelete) and [`workbook:bookmark:onupdate`](https://help.sigmacomputing.com/docs/inbound-and-outbound-events-in-embeds#workbookbookmarkonupdate), to communicate and interact between embedded content and the host application.

For more information, see [Implement inbound and outbound events in embeds](https://help.sigmacomputing.com/docs/inbound-and-outbound-events-in-embeds).

## Workbook features

### Updated application of the **On close** action trigger for modals

The **On close** trigger type for modals has been updated to only initiate actions when a user clicks the **Close** icon or anywhere outside the modal. The trigger no longer applies when the **Close** modal action is configured for the primary or secondary button.

If you configured actions for the **On close** trigger that are intended to initiate when a user clicks a button to trigger a **Close modal** action, you can move the actions to the applicable button trigger.

## Bug fixes

* The [Create connection](/reference/create-connection) endpoint (`POST /v2/connections`) and [Update connection](/reference/update-connection) endpoint (`PUT /v2/connections/{connectionId}`) no longer fail when creating or updating connections with OAuth. Note that for non-OAuth connections, the API validates that you can connect to the newly created or updated connection with your credentials. In the case of an OAuth connection, this validation step does not apply. Instead, manually validate that you can connect with your OAuth credentials after you create or update the connection.
* When the value of a grouping key is null, applying the **Selection** variable to an **Open link** action no longer returns a null value that opens a blank page.