ID 391727 - Conditional options parameters cannot be accessed if parameters contain two or more conditions

Follow

Problem summary
Conditional visibility options dialog can't be opened when there are two conditions set for a parameter.

Error message printed to the console when trying to open the Conditional Visibility Options dialog:
A TypeError occurred in "ConditionalHints.py": string indices must be integers, not str
Traceback (most recent call last):
File "bin\python\UI4\FormMaster\Editors\UserParameters.py", line 747, in __editConditionalVisibility
File "bin\python\UI4\FormMaster\Editors\UserParameters.py", line 737, in __editConditionalState
File "bin\python\UI4\FormMaster\Editors\ConditionalHints.py", line 568, in __init__
File "bin\python\UI4\FormMaster\Editors\ConditionalHints.py", line 231, in __init__
File "bin\python\UI4\FormMaster\Editors\ConditionalHints.py", line 303, in __buildPanels
TypeError: string indices must be integers, not str

This issue is regressive with Katana3.1v1

Customer reported version
katana.3.1v4

Customer reported platform

Steps to reproduce

1) Open Katana, Create a Group node

2) Add 3 User parameters ( 2 number checkboxes, 1 string )

3) Within the String User parameter, click the 'wrench' and select 'Conditional Visibility Options...'



4) Within the new window, add 2 conditions ( doesn't matter which ) and press OK.

5) Attempt to reopen 'Conditional Visibility Options...'.

Result: The 'Conditional Visibility Options...' option will no longer open, a Terminal exception will occur stating that it is a TypeError.





Expected behaviour
More than one condition should allow the window to be opened.

Actual behaviour
The window cannot be opened if more than one condition is created. 

Workaround
Unfortunately, there is no workaround apart from querying/removing the values with Python.

Reproduced by support

This bug has been reproduced in:
Katana3.1v4 - Windows 7 - CentOS7
Katana3.1v1 - Windows 7 - CentOS7

Unable to reproduce bug in:
Katana3.0v9 - Windows 7 - CentOS7

Earliest version tested
- This issue no longer appears in this version and has regressed

    We're sorry to hear that

    Please tell us why