I totally agree with Mohamed. I would like to add more like there are just a couple of very simple and common extra things worth checking as well:
Decision type: Make sure the Decision’s Type is set to Expression. Sometimes it’s easy to overlook this and leave it on a different option, which keeps the condition value disabled.
Attribute type: If you are using an attribute directly, confirm that it is actually of type Boolean. If it’s a String, Integer, or Enumeration, you must use a comparison (for example Status = 'Approved') so the result is Boolean.
The most common cause is simply that the Condition field is empty or does not evaluate to true/false yet. Once the condition returns a Boolean, the happy and unhappy path options become available automatically.
Hi,
This usually happens when the decision condition is not based on a Boolean expression.
In the Extend a Microflow step, the Condition Value (true/false) option is only enabled if:
If the decision is:
then the Condition Value shortcut will be greyed out.
$MyBoolean = true)This is expected behavior and not an issue with the template or Studio Pro.
Hi
Thank you all for your replies. After 5 minutes of posting the issue, I worked out the it was the expressions.
Thank you again.
Ypur welcome Ahmet