Virtual attributes

[Moody, Rob]

Hi,
We have just upgraded to 4.7 from 4.6B and have found that our PO =
workflow can no longer 'see' some virtual attributes that we put on our =
custom ZBUS2012 business object. A condition step which tests these =
attributes is not working because it thinks they are null, yet when we =
look at the wf container after running a test workflow we can see the =
attributes are populated. The same thing goes if we test the business =
object, the attributes are populated.  The curious thing is that a =
condition step nearer the top of the workflow can 'see' a different =
virtual attribute.  Is there something simple that we need to do to make =
this work?
Rob
 
Rob Moody
Hampshire County Council - Enterprise Project
Capital House 48/52 Andover Road=20
Winchester Hampshire SO23 7BH
Tel       +44 (0)1962 831057
email  rob.moody at hants.gov.uk
www.hants.gov.uk