Nesting When statements in Orquesta

Right now when writing check logic in orquesta I have to have a when block for each conditional. It's not graceful and harder to manage.
For ex:
Instead of ,

When ( succeeded)
      When ( x=true)
           Do thing
       When (y= true)
            Do thang

We have to do

When ( succeeded and x=true)
   do thing
When (succeeded and y = true)
   do thang

It's not clean and harder to read/maintain. Especially in some of our workflows the conditionals are large and you end up having many statements with repeated keywords in them.

Start with the nested and repeated-condition examples in the issue, then locate the workflow condition parsing and evaluation entry points in the repository. Determine how nested when blocks should be represented and evaluated, and add coverage showing the requested behavior before considering the feature done.