The ability to create ‘generic’ steps that are updated by edits on the original app. Similar to the base layout but for specific steps and cross-app updates.
Currently, we have a defect ticketing system that relies on a specific app. To prevent having to transfer apps and reload information / lower friction for technicians, the defect input step of this app has been copied to other work instruction apps. Keeping many separate apps updated as the defect ticketing app is updated is difficult to organize and tiresome.
A cross-app step layout / copy that automatically updates similar to a base layout would lower the effort required to maintain apps.
Hi @jscheel - this is a great suggestion, similar to other conversations we’ve had on Community around Widgets, Components, and shared Steps
Our future vision for shared content is to provide a feature like Components, that you’d be able to plug in and auto-update across apps… we’re in early discovery on this, and are chatting with folks about their use cases.
In the meantime a few suggestions:
-
Some customers are using what’s called “routing apps” - route to the shared step in a separate app, and then route back to your original app. This is a bit tricky and makes your app logic more complex, but lets you easily update the shared step(s)
-
We are working on a new shared business logic feature called Functions - this lets you pull out the shared logic (i.e. triggers) into a single easily updatable logic unit. Would something like this help?
We’d be happy to chat live through all the options and also better understand your use case for future shared content product work.
If this sounds interesting, please reach out to schedule - here or olga.stroilova@tulip.co
Thank you, @OlgaStroilova.
Components seems like an interesting option similar to what I’m thinking about. I am excited to hear more about this in the coming months.
Currently we do have one routing app but have decided that it’s worth the pain of updating the common steps when absolutely necessary instead of complicating some of our longer work instructions logic - we’re still new and this will likely change!
We have talked to our customer success representative about functions and they are a useful tool. However, I do not think this is a proper use case; we are sending users to a form that may be updated with new / different inputs.
I’ll reach out in the near future when I have to start maintaining my old code and want to try and find a stopgap solution.
1 Like