Cloud Fax and Notifications API 2.6 Documentation
QueuedDocumentRelease		Cloud Fax and Notifications API Forums Home  
    prev  next        Table of Contents  QueuedDocumentRelease  

46.2 QueuedDocumentReleaseRequest

QueuedDocumentRelease Overview   QueuedDocumentReleaseResult

Tag Name
& type		#Description
QueuedDocumentReleaseRequest   Namespace of this element is http://ws.easylink.com/QueuedDocumentRelease/2017/12
   SubmitId
xs:string		0-1Optional string identifying request, which will be echoed in result.
   RemoteId0-1Optional string identifying the user's process making the request. This value may be logged to help track processing, but it is not subsequently accessible to users.
   QueueId
QueueIdType		1This must contain the information exactly as returned by the QueuedDocumentRetrieve call that obtained the delivery to be released.
   XDN
xs:string		1The domain name.
   QueueName
xs:string		1The name of the delivery queue.
   ItemID
xs:unsignedInt		1An identifier for the delivery queue item.
   JobId
JobIdType		1The job to which the document belongs. See JobIdType.
This must contain the information exactly as returned by the QueuedDocumentRetrieve call that obtained the delivery to be released.
   QueuedDocumentReleaseExtensions0-1This element is used to provide the extensions that can be passed along with the QueuedDocumentReleaseRequest.
   Segment
SegmentType		1-Extensions may be divided into categories and the segment will indicate the category. See SegmentType.
   @name
xs:string		0-1The name of the segment for this property. The special name value "/Processing" is used to specify processing directives.
   Property1-This element will contain the specific extension value.
   @name
xs:string		1The name of the keyword.
The following extension can be used to specify a processing feature:
SegmentPropertyDescription
/ProcessingReleaseStatus "rejected" or "accepted". The default is "accepted" and any unrecognized value will be interpreted as "accepted". If an application cannot process a retrieved document, it can be released with a "rejected" ReleaseStatus, which will cause it to be placed on an error queue for further review while other documents can continue to be retrieved. Applications should not expect a rejected document to be re-delivered, and finding rejected documents may lead to contact to discuss the problem. Documents that are merely not useful should be released as "accepted" to permit normal processing to continue.
   @b64charset
xs:string		0-1Currently not accepted for Property elements of QueuedDocumentRelease.
 
    prev  next        Table of Contents  QueuedDocumentRelease  
© Copyright 2020 OpenText Corp. All Rights Reserved.
Privacy Policy | Cookie Policy		 This information is subject to change. Please check frequently for updates.
Modified October 06, 2020