Schema Central > OAGIS® 10 > ProcessPartyScreenResponse.xsd > ProcessPartyScreenResponse
Advanced search
Need XML Help?

Recommended Reading:

Definitive XML Schema

 

Web Service Contract Design and Versioning for SOA

 

Advanced XML Applications

 

ProcessPartyScreenResponse

The purpose of the ProcessPartyScreenResponse is to transmit an PartyScreenResponse. Indicating that the receiver of the PartyScreenResponse is to Process the PartyScreenResponse.

Element information

Type: ProcessPartyScreenResponseType

Properties: Global, Qualified, ID: oagis-id-c2b8e6409b4948c4a45770e1ef42a737

Content

Attributes

NameOccTypeDescriptionNotes
releaseID [1..1]NormalizedStringTypeOAGIS Release this BOD Instances belongs or the OAGIS release that the derivative work is based on.from type BusinessObjectDocumentType
versionID [0..1]NormalizedStringTypeIndicates the version of the given BOD definition.from type BusinessObjectDocumentType
systemEnvironmentCode [0..1]SystemEnvironmentCodeContentTypeIndicates whether this BOD is being sent in a "Test" or a "Production" mode. If the BOD is being sent in a test mode, it's information should not affect the business operation. However, if the BOD is sent in "Production" mode it is assumed that all test has been complete and the contents of the BOD are to affect the operation of the receiving business application(s).Default value is "Production". from type BusinessObjectDocumentType
languageCode [0..1]LanguageCodeContentTypeIndicates the language that the contents of the BOD is in unless otherwise stated.Default value is "en-US". from type BusinessObjectDocumentType

Sample instance

<ProcessPartyScreenResponse releaseID="normalizedString">
   <ApplicationArea>
      <Sender>
         <LogicalID>normalizedString</LogicalID>
         <ComponentID>normalizedString</ComponentID>
         <TaskID>normalizedString</TaskID>
         <ReferenceID>normalizedString</ReferenceID>
         <ConfirmationCodes>...
         </ConfirmationCodes>
         <AuthorizationID>normalizedString</AuthorizationID>
      </Sender>
      <Receiver>
         <LogicalID>normalizedString</LogicalID>
         <ComponentID>normalizedString</ComponentID>
         <ID/>
      </Receiver>
      <CreationDateTime></CreationDateTime>
      <Signature>
         <!--any element-->
      </Signature>
      <ScenarioID>normalizedString</ScenarioID>
      <CorrelationID>normalizedString</CorrelationID>
      <BODID>normalizedString</BODID>
      <Extension>
         <AnyExtension>
            <!--any element-->
         </AnyExtension>
         <Amount/>
         <Code/>
         <DateTime></DateTime>
         <ID/>
         <Indicator>true</Indicator>
         <Measure/>
         <Name/>
         <Number>1.0</Number>
         <Quantity/>
         <Text/>
         <Time></Time>
         <ValueText>string</ValueText>
      </Extension>
   </ApplicationArea>
   <DataArea>
      <Process>
         <ActionCriteria>...
         </ActionCriteria>
      </Process>
      <PartyScreenResponse>
         <ID/>
         <IDSet>...
         </IDSet>
         <Status>...
         </Status>
         <ScreeningReferenceID>normalizedString</ScreeningReferenceID>
         <ScreenParty>...
         </ScreenParty>
         <ScreenResolution>...
         </ScreenResolution>
         <ScreenDateTime></ScreenDateTime>
         <AutomaticResolveIndicator>true</AutomaticResolveIndicator>
         <PotentialMatch>...
         </PotentialMatch>
         <Extension>.......................................
         </Extension>
      </PartyScreenResponse>
   </DataArea>
</ProcessPartyScreenResponse>

Site developed and hosted by Datypic, Inc.

Please report errors or comments about this site to contrib@functx.com