Activation Condition Predicate for an Empty Attribute

[Cantor, Scott]

> Looking at the test case slightly differently, the current behavior means (in
> effect) that at least when using a RDBMS connector, a wildcard test will
> return true on any attribute, period, so long as that attribute is included in
> the query against the underlying table / view. I won't argue the semantics of
> what to call it, but that seems to render wildcard matching (for RDBMS
> connections) useless.

The results of a DataConnector are not visible to that condition. Only IdPAttributes produced by AttributeDefinitions are.

> Backing up and being a bit more specific about my use case, I'd like to use an
> activation condition on a secondary definition of the mail attribute, if and
> only if the regular mail attribute is empty and a separate additional condition
> is met.

Normally what you would do is backfill the single attribute internally so that the rest of the system just sees that final computed answer, whatever it is.

My point here is that I thought if you layered a Simple AttributeDefinition on top of a null-valued data connector source attribute, you would get no attribute out at all. I didn't realize it would copy the empty/null slots out into the visible IdPAttribute.

Nor do I know if V2 did that, to be honest.

-- Scott