Email address not passing - virtual attribute problem?

[Cheri Myers]

I have a workflow for an Admissions Application for SLCM currently in
development. It uses Business Object BUS7051 creating notifications with
all of the data from the application. We have a subtype to the Business
Object with quite a few added virtual attributes that look up
information from the notification to use in the container for workflow.
One of these values is the email address. The first step in the workflow
is to send an email using the email address in the virtual attribute.
However, 1 in 8 of these error because of a blank address. I know that
my bindings are not a problem because most of the time it works fine,
even using the same email address. When I look at the container in the
technical log, the email address is there. 

There is quite a bit of code behind each of the virtual attributes
because it looks up all of the SPECIAL DATA for each notification and
then loops through to get the value needed. My guess is that the problem
is that when the event triggers workflow, sometimes workflow gets to the
email step and errors before all of the virtual attributes can be
created with the logic used behind them. We have also had similar
problems later in the process. I have had trouble trying to figure out
why because these are intermittent problems that don't happen to every
workflow. 

Does this theory make any sense? My question is: when the workflow
triggers does it wait at each step for the virtual attributes to be
generated before continuing?  Is there another reason that I'm not
thinking of that this may be happening?  Any suggestions?


Thanks,
Cheri L. Myers
Northern Kentucky University
IT - PRISM Project
Phone: 859-572-7673
Email: myersc1 at nku.edu