The Trigger Editor allows you to write powerful logic within your manufacturing app. It allows you to create actions that incorporate many other parts of the Tulip platform, like:
- Station names
- Badge IDs
- Connector functions
- ...and much more.
There are three types of statements you can create:
When: Determine when the trigger can run
If: Determine whether an action should run or not
Then: Specify which actions should be triggered by a certain event.
This guide will cover the full list of possibilities for each type of statement. If you would like to learn how to create a Trigger, check out this separate guide.
Fire upon specific event from connected device
Fire event on pre-determined time intervals
Fire event when step is open and event occurs in machine that is actively monitored
step is opened
Fire upon step opening
step is closed
Fire upon step closing
button is pressed
Fire upon operator pressing a button
Check whether a table contains a record with a specific ID
Check whether a table record loaded into the app has a field with a specific value
Expression, Static Value, Variable
Check or compare any of these values to another variable or static value
Use a value from any of these metadata that are determined when the app is run in the Player:
- Logged In User: Select from a list of Tulip users
- Logged In User/Badge ID: The badge ID of the logged-in user
- Logged In User/Name: The name of the logged-in user
- Time Elapsed on Step: The total amount of time spent on a specific step
- Time Elapsed on Current Step: The total amount of time spent on the current step
- Time Elapsed on App: The total amount of time spent in the app during this runtime
- App Name: The name of the app
- App Version: The current version of the app
- Station Name: The name of the station where the app is running
- Step Name: The name of the current step
- Shift Name: The name of the current shift, as defined in the Schedules tool
Cancel, complete or complete and go to splash screen.
- Cancelling the app does not save any data.
- Completing the app stores data and returns to the first step and immediately runs the app again.
- The splash screen forces the operator to press "Begin" before starting the app.
Manipulate an existing array that is stored in a variable using common array methods.
Modify a variable or a table record that is loaded into the app. This is one of the most common uses of the Trigger Editor.
Go To Step
Go to the next, previous or a specific step
Logout Current User
Logout the current user and return to the login screen. Frequently used for security purposes.
Load a specific website in new window in Google Chrome
Play a predetermined sound through the user's speakers
Open the default Player Menu
Run Connector Function
Run a connector function that has been created using the Connectors feature
Run Gateway Function
Run a specific function with a connected device that is attached to an IoT Gateway at the same Station as the app.
Presents the operator with prompt to scan a barcode via the webcam on their laptop or tablet
Send a text email to a Tulip administrator
Send a text to a Tulip administrator that has added their phone number
Send SMS With Image
Send a text and image to a Tulip administrator that has added their phone number
Show a red error message at the bottom of the Player
Show a yellow information message at the bottom of the Player
Split a string based on a specific delimiter into an array and store it in a variable
Create or load a new table record using a record placeholder that has been defined in the App Builder