Regarding Tulip Player Application - Viewing Later Steps for Operators

Could you help me determine if it’s possible to preview upcoming steps in the Tulip player application for operators? Furthermore, can you provide insights into how this application is deployed in the production environment? Specifically, I’m interested in whether it’s accessed through a web portal or Tulip’s player. Additionally, I’d appreciate some recommendations on how operators can preview upcoming steps within the application.

Hi @mkalimuthu, thanks for your question. There is no native functionality for previewing steps, but there certainly are work arounds. Can you say a little more about what you’re hoping to achieve by allowing operators to preview steps?

With regards to deploying applications, you can find more info in this Tulip University course and these Knowledge Base Articles

1 Like

@mkalimuthu
Maybe this Custom Widget can help you:

Regards Chris

2 Likes

@John Thanks for the response, we are currently validating use cases for our customer, and they have expressed interest in allowing operators to preview upcoming steps. The goal is to enable operators to see what’s coming next and prepare themselves for critical tasks. By providing this feature, we aim to enhance preparedness, reduce errors, improve efficiency, and boost operator confidence. Although there isn’t a native preview functionality, exploring workarounds or custom solutions could significantly benefit the operator experience.

@ChrisF thanks for sharing that, this is the first I’ve seen that widget. This looks like a really great solution to the question.

@mkalimuthu, if this is related to your previous question, one thing you might consider is embedding a step group of previews in the menu widget while having the operator move through a step group specifically for production. That way you can still validate whether or not the operator’s task is complete on steps before moving one while still making the preview available.

@John @ChrisF

I have a quick question about the functionality of the back button in Tulip. Whenever I navigate back to a completed step, it seems that the completed step restarts, requiring me to redo it. Is there a way to view my previous actions, such as operator inputs or selected options, without restarting the completed step? It would be helpful if there were options to make previous completed steps uneditable, allowing for a review of past actions, and provide the option to restart only if I intend to redo that specific step.

There are a few things that could be going on here. One thing to consider is when data in variables and table records are cleared in Tulip. Every time you complete an application, variables that are set to reset to defaults will reset. There are also trigger actions for clear variables and clear record placeholder that could be clearing your data between steps.

If you’d like data to be persistent between steps, I’d look at storing values in a table and keeping the record placeholder loaded between steps.

It would be helpful if there were options to make previous completed steps uneditable, allowing for a review of past actions, and provide the option to restart only if I intend to redo that specific step.

If you’d like to create an immutable record of data collected on a step, you can use the save all app data action. The data won’t be accessible in the app, but you will have that record of the activity.