Platform Release 305 - February 2025

Announcements
1

:tada: Exciting news - Release 305 is here!

The Tulip team has rolled out some fresh updates across multiple features, along with some bug fixes. Check out the release notes and dive into what’s new.

Share your thoughts and questions below :arrow_down: :slightly_smiling_face:

2

I am interested in this one.

PLAT-41277 Several semantic errors with the OpenAPI documentation linked from the API Docs page have been fixed.

Can you provide us more detail?

3

Hello,
Since this update, the trigger “Complete App Then Go To First Step Of App By Name” or any trigger that goes to another app does not work IF the app that is called as an apostrophe in its name.
Thanks for fixing this issue.
Julien

4

The OpenAPI documentation available at {your-instance}/docs/api/api.json contained several semantic errors that have been fixed. Specifically:

  • Fixed a redundant type specifier on the filters and sortOptions properties in various schemas.
  • Fixed the descriptions of the id and parent properties of the AppGroup schema.
  • Fixed the descriptions of the id, createdAt, createdBy, updatedAt, and updatedBy properties of the CRUDModel schema.
  • Fixed the type and description of the filterAggregator property of the TulipTableQuery schema.
  • Fixed incorrect name and syntax for path parameters on the table link endpoints.
1 Like
5

Hello @JulienB,
Our Support and Engineering teams were informed about this issue and took action. This should be now working, but let me know if you are still experiencing it.

Thanks,
Fanni

1 Like
6

Thank you.

I do not know if this is related, but “Add string item” (and “Add object item”) buttons in the apiDocs page is broken.

image
image1116×329 25.5 KB

If I Execute the API using that button, I get 400 error.
image
image1089×425 22.3 KB

7

Hi,
After this update, Data manipulation - increment data, is broken.

8

Hi @rcanaway, do you mean Data Manipulation in Automations, or elsewhere in the product?

9

Hi, the data manipulation in the app editor. All existing triggers that use data manipulation - Increment Data, now needs to be remade as Data Manipulation - Store - Expression - Table record + 1 - store in: Table record: Current table. We have multiple apps and this issue is consistent across all published applications.

1 Like
10

Hi Ryan, can you DM me a URL for an example app or step where this is happening? That will help us investigate.

11

Hello, I’m having the same issue as Ryan… It’s not incrementing table values in the trigger

12

Thanks for flagging. We believe we’ve found and fixed the issue, and are rolling out a fix.

13

Short feedback regarding the new feature: “App trigger expression error handling”. It would be nice if you were notified, if existing triggers no longer work due to the new function (For example before deploying a new App Version). Unfortunately, the release meant that an important app in the company stopped working overnight and troubleshooting was very time-consuming.

1 Like