Hi AdamAre you sure it doesn't test against the outgoing the parameters? A lot of status change secas depend on an outgoing oldStatusId, e.g. the changeOrderStatus service secas
Regards Scott HotWax Media http://www.hotwaxmedia.com On 15/09/2009, at 11:53 AM, Adam Heath wrote:
The above service has an eca, that attempts to create a PartyContactMechPurpose, if contactMechPurposeTypeId is given. However, since most the time a contactMechId is *not* given, the seca that is configured will not fire. The seca engine doesn't support matching against the *result* of a called service, only against the incoming context. I'm considering adding support for testing against the result of a service; anyone else see the utility in this?
smime.p7s
Description: S/MIME cryptographic signature