11-13-2012 10:48 AM
How come the destination is not available while handling those events?
This makes it impossible to implement a reliable integrity enforcement policy, waiting for the CREATED event means having a possibly corrupt or incomplete document available to other handlers.
The information is readily available in AbstractSession when notifyEvent is called, is there any reason for not including the destination in the event context (or at least in the context's properties)?
Thanks!
11-14-2012 07:17 AM
There's no good reason for them to be missing. Please open a NXP ticket to request this enhancement.
11-15-2012 09:08 AM
Just did so
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.