using System;
using System.Collections;
using System.Collections.Generic;
using System.Runtime.Serialization;
using ServiceStack;
using ServiceStack.DataAnnotations;
using IDB.API.DMS.Operations;
namespace IDB.API.DMS.Operations
{
public partial class UpdateEmailConcept
{
public UpdateEmailConcept()
{
LinkedDocumentIDs = new List<string>{};
}
public virtual string PidTag { get; set; }
public virtual Guid AttachmentDocID { get; set; }
public virtual int ShippingFormID { get; set; }
public virtual List<string> LinkedDocumentIDs { get; set; }
}
}
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /xml/oneway/UpdateEmailConcept HTTP/1.1
Host: digiofficeapigateway.deltares.nl
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<UpdateEmailConcept xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/IDB.API.DMS.Operations">
<AttachmentDocID>00000000-0000-0000-0000-000000000000</AttachmentDocID>
<LinkedDocumentIDs xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
<d2p1:string>String</d2p1:string>
</LinkedDocumentIDs>
<PidTag>String</PidTag>
<ShippingFormID>0</ShippingFormID>
</UpdateEmailConcept>