That sounds much easier to fix :-)

Additionally we should probably change contactMechId to be optional IN but required OUT

Regards
Scott

On 15/09/2009, at 12:13 PM, Adam Heath wrote:

Scott Gray wrote:
Hi Adam

Are 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

Ok, yes, I was wrong about the details.

createPartyContactMech detects that a matching ContactMech already
exists for a party(based on infoString), logs that it matches, and
returns success, without returning the contactMechId.


Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to