# Restricted 'previous' trigger

**URL:** <https://community.tulip.co/t/restricted-previous-trigger/16645>\
**Category:** Product Suggestions\
**Created:** [October 16, 2026, 9:02am UTC](https://community.tulip.co/t/restricted-previous-trigger/16645 "2026-10-16T09:02:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![oscar.deakin](https://avatars.discourse-cdn.com/v4/letter/o/a9a28c/32.png) [@oscar.deakin](https://community.tulip.co/u/oscar.deakin)\
**Post date:** [October 16, 2026, 9:02am UTC](https://community.tulip.co/t/restricted-previous-trigger/16645/1 "2026-10-16T09:02:23Z")

</div>

Restricted ‘previous’ trigger to prevent operators from going back if they have just left a certain step

---

<div class="post-metadata">

**Author:** ![thorsten.langner](https://avatars.discourse-cdn.com/v4/letter/t/4bbf92/32.png) [@thorsten.langner](https://community.tulip.co/u/thorsten.langner)\
**Post date:** [October 18, 2026, 7:39pm UTC](https://community.tulip.co/t/restricted-previous-trigger/16645/2 "2026-10-18T19:39:59Z")

</div>

Can you explain the use case?  
I think this is already available by using the enabeled state functuionality.

---

<div class="post-metadata">

**Author:** ![oscar.deakin](https://avatars.discourse-cdn.com/v4/letter/o/a9a28c/32.png) [@oscar.deakin](https://community.tulip.co/u/oscar.deakin)\
**Post date:** [October 21, 2026, 7:37am UTC](https://community.tulip.co/t/restricted-previous-trigger/16645/3 "2026-10-21T07:37:58Z")

</div>

We use Tulip for our work instructions. If the operator is missing components, they are directed to a help dashboard, but depending on which step they previously came from I would like to block off the button, for example: if previous step was ‘…’ then transition to ‘…’

---

<div class="post-metadata">

**Author:** ![thorsten.langner](https://avatars.discourse-cdn.com/v4/letter/t/4bbf92/32.png) [@thorsten.langner](https://community.tulip.co/u/thorsten.langner)\
**Post date:** [October 21, 2026, 8:28am UTC](https://community.tulip.co/t/restricted-previous-trigger/16645/4 "2026-10-21T08:28:26Z")

</div>

You can Save the App Info.Step Name on step exit (in base Layout).  
Thema use it as condition in the Transition trigger or to block the Button enabeled state.

---

<div class="post-metadata">

**Author:** ![atrabuco](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/atrabuco/32/9497_2.png) [@atrabuco](https://community.tulip.co/u/atrabuco)\
**Post date:** [October 29, 2026, 3:37pm UTC](https://community.tulip.co/t/restricted-previous-trigger/16645/5 "2026-10-29T15:37:31Z")

</div>

Hi @oscar.deakin, thanks for explaining the use case, and thanks @thorsten.langner for jumping in. Thorsten’s approach is the one I’d recommend: on step exit in the Base Layout, save App Info.Step Name to a variable, then check that variable either in the transition trigger on the help dashboard button or in the button’s Enabled State. That lets you send operators back, or block them, based on the step they came from.

Since this already covers it, we aren’t planning a separate restricted “previous” trigger, but if you run into a case it doesn’t handle, post it here and I’ll take a look.
