Exciting news - Release 331 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 
Is the broken reference going to be automaticallly fixed when published?
PLAT-46129 Fixed a bug where apps with broken connector function references could not be published.
- In the app editor, number input widgets can be dynamically enabled and disabled.
Good News…
When will this come for Single- and Multi-Selects?
I wonder, why this is done one by one …
Hi @thorsten.langner great question. Implementing this improvement has to be carried out one by one in how the inputs are structured, so we’re rolling them out iteratively in order of priority to customers. We feather this in to the other sprint work we have, and also balance with the other “Quick Win” improvements we’re working on.
Yes our hope is to also implement for single and multi selects. We don’t have an exact timeline yet, but hopefully we’ll be able to fit this in soon.
Hi @ta-aoki ,
We’re unable to fix the broken reference because the connector function it points to was deleted, and we don’t know which function should replace it. Similar to other trigger errors (for example, when a machine is deleted), you’ll see an error message when running the application in development mode or in the player. To resolve the bug, you can identify the correct connector function to use in place of the deleted one, then update the reference.
Since we were unable to archive the used connector functions from r303, I thought all the connector functions used in the App cannot be deleted. Maybe I am not understanding these release notes correctly. Could you please explain?
Connector functions can now only be archived if they are not used by any apps or automations.
Hi @ta-aoki,
A couple of clarifications:
- The change we made in r303 to block the archive of in-use connectors was reverted in r308
- The change we made in r331 where we fixed “broken connector functions” was specifically addressing an erroneous database state for a connector, not just simply apps pointing at archived functions.
Hope this clarifies,
Cana
1 Like
I saw the “installation qualification certificate”. It is interesting.
What is the typical use case Tulip have in mind to let us see this?
Is it just for the general transparency?
Hi @ta-aoki,
This is a feature mainly for life sciences customers who need to have an installation certificate for the processes. In addition, it’s transparency behind the installation process for our customers.
Sincerely,
Jake
1 Like
In Player, a warning will be shown if a user attempts to close Player while triggers are still executing.
Does this apply to Windows Tulip Player and iPad Tulip Player ?
I tried to see the warning, but it did not appear.
(I closed the Player when repeated email sending action was still running.)