Jump to section
Release 199 and 200 of the Tulip platform are here. Alongside several bug fixes, we are excited to announce that Developer Mode, a new workflow for testing apps in the app editor, is finally available for all production users.
What is Developer Mode
Developer Mode is a new interface in the Tulip app editor. Instead of running apps in the player to see changes and ensure everything is working, you can select “Test” and view the app in a sandbox environment, within Google Chrome.
This allows you to run the app and interact with it while displaying important metrics. In addition, you can run simulated environments with different stations, operators, or connectors, without any long loading times.
How Can I Use Developer Mode
To get started with Developer Mode, open any app in the Editor and select the “Test” button.
The Developer Mode interface has 4 sections:
- Session Parameters
- Live Data
Session Parameters allows you to test the app in different scenarios. You can change the connector environment, user, and station that the app is running on.
Live Data allows you to see variables and record placeholders as they are updated while you interact with the app.
The App section lets you interact with the app as it would run on a device in Player.
Completions show app completions in Developer Mode. These completions exist only in Developer Mode and will disappear upon closing the window. You can load records from Tulip Tables and manipulate them in Developer Mode without changing them in the Table.
Want to learn more about Developer Mode? Check out this support article to get started →
Other Fixes and Changes
- “Text” response type and outputs are available in Connectors
- Timestamps are supported in HTTP Connectors
- Error messaging for Connectors is more descriptive
- Boolean input widget can connect to a table
- Added OAuth 2.0 customization 7
- Users can now launch a specific app directly from the player URL
- The run button opens the correct app in Player
- Default Working Days update correctly in account settings
- Signature Form signatures are always recorded when an app is canceled
- Machine Monitoring widget uses the proper timezone to calculate intervals
- Removed unnecessary copy/cut/paste buttons
- Date picker in Player is rendered correctly
- Improvements to loading times for the expression editor
- “Cancelled” message does not show when printing
- Error messages in dev mode display in the same place
- Shared dashboard links are visible in Incognito tabs
- Analytics editor does not crash on Tulip Tables when the second column can’t be part of an analysis
- Machine state duration is calculated in the local timezone
- Analytics are calculated in the local timezone
- Empty strings and null values can be returned from JSON connector functions
- Tulip Tables API now supports multiple sort options
- New machines open in edit mode
- The Stations page will now load faster
- Variable widgets now show a separate data source selection for App Info
- Special characters can be used in the Connector editor
- Tables display the correct number of records
- Connector or Machine Header names no longer push buttons out of view
- Less delay when using URLs navigating directly to an app in Player
- The Player does not use extra memory when displaying dynamic analysis
- Operators can always switch from the Player app menu
These features and more are available to Tulip users in release 200 and above. To learn more about other additions and fixes with the most recent releases of Tulip, visit our community site for release notes, and our support site for resources. Want to learn more about a specific product feature? Reach out with questions.