ApplicationAreaDataArea| Description |
| SyncScreeningPackageOrder is used when the owner of the data is passing or publishing that information or change in information to other software components. This is to be used when the receiver of the SyncScreeningPackageOrder does not own the data. This verb is commonly used when mass changes are necessary or when a publish and subscribe mechanism is used in the integration architecture. The purposes of this verb include application integrity and ease of data entry for the business user by enabling a single point of input. ScreeningPackageOrder This is a subset of the full ScreeningOrder. It is intended to support an "OrderByPackageID" scenario. As the name implies, the "order by package" pattern involves bundling all screening service options within predefined packages that are known to the customer and to the screening provider. This enables services to be ordered simply by referencing an associated "PackageID." When using this pattern, details about specific screening services do not have to be communicated within the order. This simplifies order creation significantly and provides the opportunity to use an interoperable subset of the full ScreeningOrder noun. |
| Type : SyncScreeningPackageOrderType |
| Definition |
|
SyncScreeningPackageOrder is used when the owner of the data is passing or publishing that information or change in information to other software components. This is to be used when the receiver of the SyncScreeningPackageOrder does not own the data. This verb is commonly used when mass changes are necessary or when a publish and subscribe mechanism is used in the integration architecture. The purposes of this verb include application integrity and ease of data entry for the business user by enabling a single point of input.
ScreeningPackageOrder This is a subset of the full ScreeningOrder. It is intended to support an "OrderByPackageID" scenario. As the name implies, the "order by package" pattern involves bundling all screening service options within predefined packages that are known to the customer and to the screening provider. This enables services to be ordered simply by referencing an associated "PackageID." When using this pattern, details about specific screening services do not have to be communicated within the order. This simplifies order creation significantly and provides the opportunity to use an interoperable subset of the full ScreeningOrder noun.
(Defined in file SyncScreeningPackageOrder.xsd , or a file it imports) |
| Elements | |||
| ApplicationArea | Provides the information that an application may need to know in order to communicate in an integration of two or more business applications. The ApplicationArea is used at the applications layer of communication. While the integration frameworks web services and middleware provide the communication layer that OAGIS operates on top of. | ||
| DataArea | The DataArea is the part of the BOD that contains business information. This information consists of a verb and one or more noun instances. | ||
| Attributes | |||
| languageCode | Indicates the language that the contents of the BOD is in unless otherwise stated. | ||
| releaseID | OAGIS Release this BOD Instances belongs or the OAGIS release that the derivative work is based on. | ||
| systemEnvironmentCode | Indicates 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). | ||
| versionID | Indicates the version of the given BOD definition. | ||