State:New|TargetRelease:No Target|icon_bug|icon_katana|database:public|Resolution:Fixed|BugID:371671|
Problem summary
Conditional visibility conditioned on TeleParameter remains hidden despite condition being met.
Customer reported version
Katana 3.0v6
Customer reported platform
Fedora
Steps to reproduce
0) Open the example Katana project conditionalVisibilityConditionedOnTeleparameter.katana.
And skip to Step 6
1) Create a Dot node and Edit User Parameters
2) Add a Number parameter, rename it to "check", and change type to "Check Box"
3) Add a String parameter, rename it to "value", and set to "hello world!"
4) Add a TeleParameter, connect it to the "check" parameter, and rename it to "check_tele"
5) Condition the "value" parameter to: if parameter "../check_tele" is "equalTo" "1"
6) Finish Editing User Parameters
7) Click check
Notice the "value" parameter remains hidden.
Workaround
If the TeleParameter is connected to a different node, then there is no known workaround.
Otherwise, condition to the original parameter.
Reproduced by support
This bug has been reproduced in:
Katana 3.0v6 - Windows 10, CentOs 7
Katana 3.0v1 - Windows 10, CentOs 7
Katana 2.6v4 - Windows 10, CentOs 7
Katana 2.6v1 - Windows 10, CentOs 7
Katana 2.5v7 - Windows 10, CentOs 7
Katana 2.5v1 - Windows 10, CentOs 7
Katana 2.1v6 - CentOs 7
Katana 2.1v1 - CentOs 7
Katana 2.0v5 - CentOs 7
Katana 2.0v1 - CentOs 7
Katana 1.6v3 - CentOs 7
Earliest version tested
- This issue appears to be in all versions of the product
Expected behaviour
The parameter is shown when the condition is met on a TeleParameter.
Actual behaviour
The parameter remains hidden when the condition is met on a TeleParameter.
We're sorry to hear that
Please tell us why