Target Namespace | http://cufxstandards.com/v5/SecureMessage.xsd |
---|---|
Version | 5.0.Revision |
Element and Attribute Namespaces |
|
Schema Composition |
|
Prefix | Namespace |
---|---|
Default namespace | http://cufxstandards.com/v5/SecureMessage.xsd |
xml | http://www.w3.org/XML/1998/namespace |
xs | http://www.w3.org/2001/XMLSchema |
common | http://cufxstandards.com/v5/Common.xsd |
party | http://cufxstandards.com/v5/Party.xsd |
relationship | http://cufxstandards.com/v5/Relationship.xsd |
account | http://cufxstandards.com/v5/Account.xsd |
card | http://cufxstandards.com/v5/Card.xsd |
document | http://cufxstandards.com/v5/Document.xsd |
artifact | http://cufxstandards.com/v5/Artifact.xsd |
user | http://cufxstandards.com/v5/User.xsd |
productServiceRequest | http://cufxstandards.com/v5/ProductServiceRequest.xsd |
accessProfile | http://cufxstandards.com/v5/AccessProfile.xsd |
Name | secureMessageList |
---|---|
Type | SecureMessageList |
Nillable | no |
Abstract | no |
Documentation | The secure messages collection/array list contains all the secure messages or secure message templates, for instance, that the credential set is authorized to access at the Institution based on applied filters. |
Name | BodyContainsList |
---|---|
Abstract | no |
Documentation | The list of bodyContains strings somewhere within its body and that should have their associated secure messages either returned or affected by a read, update or delete secure message request. |
Name | SecureMessage |
---|---|
Abstract | no |
Documentation | The secure message defines the information sent and then received by two or more parties. It also relates secure messages to the sending and receiving party(ies), and potentially to the relationship and/or account(s) to which the secure message is bound. |
Name | SecureMessageIdList |
---|---|
Abstract | no |
Documentation | The list of secure message IDs that should have their associated secure messages either returned or affected by a read, update or delete request. |
Name | SecureMessageList |
---|---|
Abstract | no |
Documentation | The secure messages collection/array list contains all the secure messages or secure message templates, for instance, that the credential set is authorized to access at the Institution based on applied filters. |
Name | SecureMessageStatusList |
---|---|
Abstract | no |
Documentation | The list of secure message statuses that should have their associated secure messages either returned or affected by a read, update or delete request. |
Name | SecureMessageTypeList |
---|---|
Abstract | no |
Documentation | The list of secure message types that should have their associated secure messages either returned or affected by a read, update or delete request. |
Name | SecureMessageUser |
---|---|
Abstract | no |
Name | SecureMessageUserList |
---|---|
Abstract | no |
Documentation | Can serve as a list of users that either receive or send a message. Can also serve as a list of secure message users that should have their associated secure messages returned or affected by a read, update or delete request when filtering. |
Name | StatusLog |
---|---|
Abstract | no |
Documentation | The dates and times corresponding to the secure message's statuses, i.e. drafted, sent, read, replied, forwarded, etc. |
Name | StatusLogEntry |
---|---|
Abstract | no |
Documentation | The dates and times that the secureMessage changed status to drafted, sent, read, replied, forwarded, etc. |
Name | SubjectLineContainsList |
---|---|
Abstract | no |
Documentation | The list of secure message subjects that should have their associated secure messages either returned or affected by a read, update or delete request. |
Name | ThreadIdList |
---|---|
Abstract | no |
Documentation | The list of thread IDs that should have their associated secure messages either returned or affected by a read, update or delete request. |
Name | BodyFormat |
---|---|
Content |
|
Documentation | The format of the body content. |
Name | SecureMessageId |
---|---|
Content |
|
Documentation | The secure message ID is a persistent and unique identifier for the secure message that is not related to the party, relationship or accounts that the secure message is for. It should be unique for all secure messages across the institution and remain the same over the life of the secure message within the financial institution. |
Name | SecureMessageStatus |
---|---|
Content |
|
Documentation | Current status of the secure message, i.e. a template or in the process of being sent, viewed, returned (see signature type to determine if it was signed or not when returned), etc. |
Name | SecureMessageType |
---|---|
Content |
|
Documentation | Type of secure message or secure message template, such as Product Offer, Notice, etc. |
Name | SubjectLine |
---|---|
Content |
|
Documentation | Each secure message has a subject line supplied by the creator of the secure message. |
Name | ThreadId |
---|---|
Content |
|