Scoped attributes available to other definitions?

[Cantor, Scott]

On 1/10/14, 3:27 PM, "Baron Fujimoto" <baron at hawaii.edu> wrote:
>
>I've attempting to construct an email attribute from a previously defined
>scoped attribute, but the resulting email attribute value only contains
>the unscoped value.

Most of the plugins only operate on "simple" values, they don't know about
the scope. You would probably have to use a Script attribute and have it
explicitly use the APIs to create and access values as
ScopedAttributeValue objects.

In most cases, building the EPPN from scratch instead of using a
pre-scoped value, and then multi-sourcing attributes off of that source
material is easier than trying to get to a scoped EPPN and then using it
as a dependency.

-- Scott