Currently, the IsEnabled ChangePropertyAction offers a Boolean which when unchecked, corresponds to IsEnabled=False, and when checked, to IsEnabled=True.

When setting up a Trigger with a ChangePropertyAction that fires off a change to an Element's 'isEnabled' Property, the Action defaults to being IsEnabled=False (Unchecked).

However, when Playing the Page, it appears as though the Default 'Unchecked' isn't actually being registered as a Trigger value.

To resolve this issue, the user must first Check the boolean (setting IsEnabled=True), then check it again (to actually register IsEnabled=False)

Repro Steps:

1) Create a Studio Project featuring a MainPage.xaml

2) Introduce a Button and a CheckBox to the Page, and name each of them in the Navigator with unique names.

3) Select the CheckBox, find its 'Enabled' Property in its Properties Panel, and check it on and off to ensure its working and displaying a 'Disabled' state when unchecked.

4) Select the Button, and navigate to the Interactions/Triggers Panel, and create a new Event Trigger, set with an Event of 'Click'.

5) Add an Action to the Trigger, with a 'Target' of the CheckBox, with a 'Property Name' of 'IsEnabled', and leaving the 'Value' as 'Unchecked'.
In theory, an 'Unchecked' Value should represent IsEnabled=False, and this Trigger should make the CheckBox disable when the Button is clicked.

6) Play the Page, and click on the Button.
Observe how the CheckBox does not transition to its Disabled State.

7) Open the Trigger again, and this time, check the 'Value' Property.
This will now colour-code the 'Value' Property Blue.

8) Click the 'Value' checkbox again, to set the 'Value' to 'unchecked'.
Observe how this time, unchecked is adorned with Blue too.

9) Play the Page, and click on the Button.
Observe how now the Trigger is correctly reading the 'Unchecked' value in the Trigger, and correctly setting the CheckBox to disabled.

Expected Results: Unchecked Property Value are immediately recognised and registered for their value.