Sample Soap Request for Method: updateRecipientLiverHealth( WsRecipientMeld wsInput)
Request: input INVALID - wsInput.comments length > 1000 characters.
<![CDATA[
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ctr="http://ctr3ws.cbs.com/">
<soapenv:Header><wsse:Security soapenv:mustUnderstand="0" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> <wsse:UsernameToken wsu:Id="UsernameToken-3" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <wsse:Username>WS_QC</wsse:Username> <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">Anypw123!</wsse:Password> </wsse:UsernameToken> </wsse:Security> </soapenv:Header>
<soapenv:Body>
<ctr:updateRecipientLiverHealth>
<arg0>
<nationalRecipientId>CTR060749</nationalRecipientId>
<meldScore>77</meldScore>
<ltMeldCalculationMethod>
<id>1</id>
<!--<bizRef>MELD_3.0</bizRef>-->
</ltMeldCalculationMethod>
<meldCalculationDate>2026-08-25</meldCalculationDate>
<comments>This is a sample comment created specifically to test a field that accepts a maximum length of 1000 characters. The purpose of this comment is to provide realistic text that can be copied directly into an application, database field, form, or test case without requiring any additional changes. It contains multiple sentences so that the content resembles a normal business comment rather than a simple sequence of repeated characters. The comment can also be used to verify whether the application correctly handles long text, preserves spaces and punctuation, validates the expected character limit, and displays the complete content without unexpectedly truncating or modifying it. When testing a maximum-length field, it is useful to confirm both the exact character count and the behavior when the limit is exceeded. This example intentionally reaches the requested boundary and can therefore be used as a positive test case. Additional testing could include submitting an empty comment, a very short comment, a comment containing special characters, and a comment that exceeds the permitted length by one character. This should help confirm that validation, storage, retrieval, and display behavior all work correctly under normal and boundary conditions. The text remains intentionally neutral, professional, and suitable for general-purpose testing.</comments>
</arg0>
</ctr:updateRecipientLiverHealth>
</soapenv:Body>
</soapenv:Envelope>
]]>
Response: Recipient's Liver Health record -> Error.
<![CDATA[
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>
Method: updateRecipientLiverHealth;
SoapLogID: 2493791;
ErrorID: error.common;
Msg: Input argument [WsRecipientMeld.comments] length exceeds max [1000];
MsgHtml: Input argument [WsRecipientMeld.comments] length exceeds max [1000];
</faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>
]]>