# Lock a checkbox?

**URL:** <https://community.tulip.co/t/lock-a-checkbox/958>\
**Category:** Support, Troubleshooting, & Help\
**Created:** [November 2, 2020, 9:29am UTC](https://community.tulip.co/t/lock-a-checkbox/958 "2020-11-02T09:29:59Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![ChrisF](https://avatars.discourse-cdn.com/v4/letter/c/d6d6ee/32.png) [@ChrisF](https://community.tulip.co/u/ChrisF)\
**Post date:** [November 2, 2020, 9:30am UTC](https://community.tulip.co/t/lock-a-checkbox/958/1 "2020-11-02T09:30:00Z")

</div>

Hi there,  
is it possible to lock a checkbox for changing the value?  
I have a test protocol for 2 test runs and the input from the first test run should not be able to modify during the second test run.  
Or is it a workaround?

Regards Chris

---

<div class="post-metadata">

**Author:** ![gio](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/gio/32/82_2.png) [@gio](https://community.tulip.co/u/gio)\
**Post date:** [November 2, 2020, 10:46am UTC](https://community.tulip.co/t/lock-a-checkbox/958/2 "2020-11-02T10:46:27Z")

</div>

hey @ChrisF,

there are certainly several ways this can be implemented depending on the structure of your app. the two simplest solutions are:

1. make a new step for the 2nd test and overlay a transparent box over the Checkbox as to prevent the user from manipulating the Checkbox
2. increment a Number variable after the first test to 2, and store the value you’d like stored in the Checkbox prior to completing the app (or storing to a Table Record). for example:  
 ![Screen Shot 3](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/1X/300b94c74b85b689d920338e3deff13a19f16e73.jpeg)

would either of these solutions work??

this sounds like a great use case to review in Office Hours, are you available Thursday at 10AM EU time to discuss this?? let me know and I can add you to the invite!!

gio

---

<div class="post-metadata">

**Author:** ![ChrisF](https://avatars.discourse-cdn.com/v4/letter/c/d6d6ee/32.png) [@ChrisF](https://community.tulip.co/u/ChrisF)\
**Post date:** [November 2, 2020, 11:03am UTC](https://community.tulip.co/t/lock-a-checkbox/958/3 "2020-11-02T11:03:10Z")

</div>

Ah, that could work.  
I will play with this option and reply.  
Tanks  
Chris

---

<div class="post-metadata">

**Author:** ![ChrisF](https://avatars.discourse-cdn.com/v4/letter/c/d6d6ee/32.png) [@ChrisF](https://community.tulip.co/u/ChrisF)\
**Post date:** [November 12, 2020, 12:56pm UTC](https://community.tulip.co/t/lock-a-checkbox/958/4 "2020-11-12T12:56:08Z")

</div>

ok,  
1st solution works only when i use the overlay manually, because the overlay is on the top of the widgets and i can not move it in the background. So i can not use the APP for 2 tester by checking the tester.  
The second is not clear for me, so i have to think about this in a quit moment.

Regards  
Chris

---

<div class="post-metadata">

**Author:** ![gio](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/gio/32/82_2.png) [@gio](https://community.tulip.co/u/gio)\
**Post date:** [November 12, 2020, 1:52pm UTC](https://community.tulip.co/t/lock-a-checkbox/958/5 "2020-11-12T13:52:48Z")

</div>

hello @ChrisF,

just to confirm, are you aware of Layers in Tulip?? that is, widgets can be moved Forward and Back using the Layer options, more info: [https://support.tulip.co/en/articles/2186385-intro-to-the-tulip-app-builder](https://support.tulip.co/en/articles/2186385-intro-to-the-tulip-app-builder). example:

 ![Screen Shot](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/1X/f72eab5d7198f9df781f60757848ce5899a781d8.jpeg)

---

<div class="post-metadata">

**Author:** ![ChrisF](https://avatars.discourse-cdn.com/v4/letter/c/d6d6ee/32.png) [@ChrisF](https://community.tulip.co/u/ChrisF)\
**Post date:** [November 12, 2020, 2:12pm UTC](https://community.tulip.co/t/lock-a-checkbox/958/6 "2020-11-12T14:12:38Z")

</div>

yes, but i can do it only inside the app builder not inside a trigger (?).

REgards Chris

---

<div class="post-metadata">

**Author:** ![gio](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/gio/32/82_2.png) [@gio](https://community.tulip.co/u/gio)\
**Post date:** [November 12, 2020, 2:17pm UTC](https://community.tulip.co/t/lock-a-checkbox/958/7 "2020-11-12T14:17:16Z")

</div>

@ChrisF, you can also drag and drop Triggers on a Button (or any other Trigger) to re-arrange the order in which they happen.

are you attempting to change the order in which Triggers occur??

---

<div class="post-metadata">

**Author:** ![ChrisF](https://avatars.discourse-cdn.com/v4/letter/c/d6d6ee/32.png) [@ChrisF](https://community.tulip.co/u/ChrisF)\
**Post date:** [November 16, 2020, 1:28pm UTC](https://community.tulip.co/t/lock-a-checkbox/958/8 "2020-11-16T13:28:54Z")

</div>

the trigger is not the problem.  
My idea was to change the position of a layer by code or to lock a checkbox like  
checkbox1.disable=true (disable the possibility to change the value).

Please take it as a request: lockable widgets (input fields, checkboxes) by code

Regards Chris

---

<div class="post-metadata">

**Author:** ![kevin.kononenko](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/kevin.kononenko/32/32_2.png) [@kevin.kononenko](https://community.tulip.co/u/kevin.kononenko)\
**Post date:** [November 16, 2020, 5:00pm UTC](https://community.tulip.co/t/lock-a-checkbox/958/9 "2020-11-16T17:00:26Z")

</div>

Hey @ChrisF, I am a product manager at Tulip! I think we are going to solve this by allowing you to create triggers that fire when checkboxes are pressed.

That way, you could create a boolean and only allow the checkbox to be updated if the boolean had a certain value.

Does that sound like it would solve it?

---

<div class="post-metadata">

**Author:** ![ChrisF](https://avatars.discourse-cdn.com/v4/letter/c/d6d6ee/32.png) [@ChrisF](https://community.tulip.co/u/ChrisF)\
**Post date:** [November 18, 2020, 12:37pm UTC](https://community.tulip.co/t/lock-a-checkbox/958/10 "2020-11-18T12:37:52Z")

</div>

Hi Kevin,  
i think that is a good way - thanks 🙂  
Regards  
Chris
