Exciting news - Release 380 is here!
The Tulip team has rolled out fresh updates across the platform, along with some bug fixes. Check out the release notes and dive into what’s new.
Share your thoughts and questions below 
Thanks for sharing,
I like the App Name Navigation and the Interactive Table Widget Update.
However I am not to happy with the support mail solution on SAML issues.
→ we have different support contacts for each workspace, so I prefer a workspace specific setting
(or a list, if the issue is before a workspace can be determined)
→ I would love to add more information (subject, body…) to provide a full mailto-link (this would also help routing a mail by its subject), also adding parameters
→ I would like to add some information about what the email must contain
The current solution forces us to handle new confusions.
Hey @thorsten.langner -
Thanks for all the helpful feedback re:SAML - these are a ton of good ideas that would help us keep pushing this forward.
A clarifying point and a few questions.
The clarifying point -
The initial scope here is simply added configuration for the error message shown to users when users fail to authenticate with the SAML provider. Historically this always showed a message like “Generic error [500]: reach out to support@tulip.co”. This would lead to support emails to Tulip for issues where we couldn’t really help. The scope of this initial work is to allow you to define a replacement of “support@tulip.co” and some improvements to make that error message more actionable (for your SAML admin). Today we do not automatically send an email to this email address automatically (if that wasn’t clear from the release note).
And my questions -
- Would it be useful if we did simplify the process of actually getting into a mail client? Are shop floor users running Tulip on machines where they can access their personal emails to send these messages?
- Would it be useful if these errors were automatically send to your IT support contact? This seems like the scope you are picturing based on your suggestions.
Best,
Pete
Yes we have a lot of personal laptops and tablets running TULIP.
I don’t think this is alone is the solution. At least not with enough differentiation (User, Plant, Context…)
Hey @thorsten.langner -
I don’t think this is alone is the solution. At least not with enough differentiation (User, Plant, Context…)
Totally agreed. This is where something like a template builder would be incredibly valuable - allowing you to quickly define the subject, dynamic information, etc.
Best,
Pete
App Editor
- In the App Editor, clicking the app name now navigates to the App Overview page. Renaming an app and editing its description is now done with the pencil icon next to the name. Previously, clicking the app name opened the rename and description popover.
I am not sure which part this is decribing.
Could you please add a screenshot of “before” and “after” ?
There is no difference visible. It is only the navigation that changes.
If you want to navigate to the App Page, where the Versions and Completions are displayed, you can now klick on the App Name in the editor view.
This used to open the edit app name dialog. For this type of navigation you had to klick on the folder name (from the path) and then chose the app again.
Thank you very much!
Your explanation made it clear. Now I understand.
When I first read the description, I thought it was describing about this yellow part (which opens Renane/description editing popover).
From your explanation, now I understand that the release note is telling me about this blue part. And yes, I confirm that it has changed exactly as the release note describes.
you had to klick on the folder name (from the path) and then chose the app again
We were also able to click the arrow on the left (marked green), but yes clicking the App Name is more intuitive.