When you execute a call that accesses an attribute associated with a query trigger, the client-side attribute lookup code performs the following tasks:
· Binds to the attribute trigger (using a binding from the attribute type's schema entry)
· Makes the remote sec_attr_trig_query( ) call to the attribute trigger server, passing in the attribute keys and optional information provided by the caller
· If the sec_attr_trig_query( ) call is successful, returns the output attribute(s) to the caller
If you execute a sec_rgy_attr( ) update call with an attribute type that is associated with a query trigger, not an update trigger, the input attribute values is ignored and a "stub'' attribute instance is created on the named object simply to mark the existence of this attribute on the object. Modifications to the real attribute value must occur at the attribute trigger.