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?