Cloud Fax and Notifications API 2.4 Documentation
MMCoverSheetCreate
Cloud Fax and Notifications API Forums Home  
    prev  next        Table of Contents  MMCoverSheetCreate  
These pages describe an earlier version of the Cloud Fax and Notifications API.
While that version continues to function, new development should use the current version.
 

41.2 MMCoverSheetCreateRequest

MMCoverSheetCreate Overview   MMCoverSheetCreateResult

Tag Name
& type
#Description
MMCoverSheetCreateRequest   Namespace of this element is http://premconn.premiereconnect.com/2007/02
   SubmitId
xs:string
0-1Optional string identifying request, which will be echoed in result.
   ObjectStore
xs:string
1The store in which the mmcoversheet is to be created. This can be a specific EasyLink "domain" name, but using a generic system type "XDDS" or "MR" allows the Cloud Fax and Notifications API to choose the most appropriate available switch.
   ReplaceExisting
xs:boolean
1This boolean value indicates whether a new mmcoversheet is to be created or an existing one is to be replaced.
   MMCoverSheetId
StoredObjectIdType
1MMCoverSheet object identifier. See Stored Objects. For this function, objKind must be "mmcover". Note that ownership controls who can see or use the object - "user" means that only the creating user will be able to use it.
   DisplayName
xs:string
0-1The string to be used as the display name for the mmcoversheet object.
   MainDocument
DocumentType
1This is the Word document that will be used as the mmcoversheet. See DocumentType. For this function, DocType must be MSW.
   MappingField
xs:string
2-This element is used to provide the mapping of the field names used in the mmcoversheet document. Available field names for mapping are :
  • BILLCODE
  • CREF
  • DOC_PAGES
  • FROM
  • INS
  • JOBNO
  • LDATE
  • NOTES
  • NOTES_FILE
  • ORIG_PHONE
  • PHONE
  • SDATE
  • SJOBNO
  • SUBJECT
  • TIME
  • TO
  • ATTN
 
    prev  next        Table of Contents  MMCoverSheetCreate  
© 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