Workflow condition step returns wrong value

[Kamaraj Shankar]

Hi Sarah,
 
    I have come across similar problem. First test the
attribute return values in the object builder by providing a
test applicant. If this works fine, then re-generate the object
and test the condition return values. If both the steps work,
the workflow condition step should work.
 
   Best wishes.
 
Kamaraj Shankar
 
 
 
 
 
________________________________________________
Get your own "800" number - Free
Free voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag
 
 
---- On    , Jackson, Sarah A (Sarah.Jackson at let-it-be-
thus.com) wrote:
 
> Hi,
>
> I am working with version 46b and am working on a workflow to
do the
> following - when an external applicant is created and a
reference
> employee
> is available, a mail notification should be sent to that
reference
> employee.
> The object type 'applicant' did not contain the attributes
reference
> employee available or reference employee, therefore I have
created a
> subtype
> and assigned those attributes to it. This all seems to be
working fine.
> In
> the workflow, the first step is a condition step that says if
applicant
> is
> external and reference employee is available, send mail
notification.
> (if
> Applicant.Internal External = 'AP' and Applicant.Reference
Available =
> 'X',
> send mail) If false, workflow ends. I have set up the
condition, but
> when I
> try to test the workflow, the condition step always returns
the value
> false
> and terminates immediately. I have created a number of
applicants who
> are
> external and do have reference employees yet still get return
value
> false. I
> have tried testing the condition step with just the applicant
number as
> the
> condition, and then using that applicant, yet still get the
value false.
> Any
> ideas on this would be greatly appreciated!
>
> Thanks in advance,
>
> Sarah Jackson
>
>