Bug #6717
closed
CB Conditional conditional others fields are not being ignored for completion
100%
Description
When CB Conditional hides fields using "conditional others" instead of "conditional self" the field is still being checked for completeness. This is likely due to it doing a fieldCall for the edit display of a field when it probably also needs to check the users _getTabFieldsDb array, which "conditional others" primarily affects.
Updated by krileon over 7 years ago
The edit check in CB Conditional for _getTabFieldsDb only applies during a save operation. So this may not be possible to fix. It's possible to ignore fields not visible on profile, but that's not accurate regarding completeness as a field could have edit access, but not display.
Updated by krileon over 7 years ago
- Status changed from Assigned to Rejected
- Target version deleted (
3.2.0) - % Done changed from 0 to 100
fieldDisplay in CB Conditional does not take into consideration "conditional others" and is why this is happening. It can't since those conditions come from a field other than the one being output.
This is not fixable and the recommendation is to just not use "conditional others" in favor of "conditional self". The "conditional others" usage will be removed in next major CB Conditional release.