CB TAB conditional problems!

I upgraded CB, from version 1.9.1 to version 2.0.4 and upgraded CB Conditional, from version 3.0.12 to version 4.0.5.
After the update I have problems on a Tab conditioning that worked before.
The problem is similar to what I wrote in this post
I'm sure now that the tab there are system fields.
Question: After upgrading CB there are to perform particular jobs?
I just run the updated and I have changed any configuration. Before worked does not work now!
Thanks for the support

I try to explain better.
I have two fields mandatory:
Field 1 (Tipo Registrazione)



and
Field 2 (Abilita Eventi).





If Field 1 = "Organizzazione" Field 2 is displayed and also displays Tab conditional "Organizzazione".



Conditional rendering works.
If Field 1 = "Privato" Field 2 is not displayed (this is right) but I can not save because asked to fill the field because Field 2 is mandatory even if the field is not in the condition to be displayed.

With CB Conditional version 3.0.12 this worked well

Are you conditioning the same field more than once? If you are then it's going to result in problems. A field should only be conditioned once and only the last condition applied will function. CB Conditional did this in reverse and only cared about the first condition applied (it was a bug). Does this happen when updating profile edit and/or registration?

You also appear to have CB Privacy installed. Ensure it is also up to date as it and CB Conditional both process a fields row, which could conflict.

Hi Krileon, thanks for your reply.
The configuration can be seen from the pictures I've attached.
It's very strange that the same configuration on cb 1.9.1 with cb conditional 3.0.12 worked perfectly and now no longer works.
The only thing different was the installation of Cb privacy in addition now even though it was not published.
I also uninstalled cb privacy but still does not work.
I think conditional Cb has a problem you need to solve.

Why are your 2 fields marked read only? They can't be edited during profile edit in this case. So is this condition erroring in backend profile edit and/or frontend registration only? or are you also getting the required field error in profile edit? Do the function again when you set Read Only to No?

Why are your 2 fields marked read only? They can't be edited during profile edit in this case.

I know that.
The problem is not in edit profile Frontend / Backend. The problem is the registration form, I can not complete the registration because it asks to complete a mandatory field that instead was excluded with CB conditional.
This is the problem.
I repeat that the configuration that you see in the images with CB Conditional version 3.0.12 has always worked well.
I can not understand why it does not work with the new version.
Has changed the logic of CB Conditional?
Sorry for my English, maybe the problem is this for me.