ApplicationAreaDataArea| Description |
| CancelOrganizationChart conveys an instruction to cancel a previously communicated OrganizationChart instance. Cancel is not a simple delete in that cancelation may require business calculations and require prior agreement on cancelation terms. OrganizationChart Provides a simple, "open model" structure for communicating basic information about an organization, its sub-entities or "organization units," the positions within those units, and the incumbents within those positions. The schema design is "flat" versus recursive in design, but hierarchy and reporting relationships can be expressed. Cancel is an "Action Verb". ActionExpression(s) represent and communicate data management instructions. The data entities being managed are represented as elements of the OrganizationChart noun in the BOD instance. The Cancel verb is used when the sender of the BOD is not the owner of the data, but is sending a request for the document to be canceled. |
| Type : CancelOrganizationChartType |
| Definition |
|
CancelOrganizationChart conveys an instruction to cancel a previously communicated OrganizationChart instance. Cancel is not a simple delete in that cancelation may require business calculations and require prior agreement on cancelation terms.
OrganizationChart Provides a simple, "open model" structure for communicating basic information about an organization, its sub-entities or "organization units," the positions within those units, and the incumbents within those positions. The schema design is "flat" versus recursive in design, but hierarchy and reporting relationships can be expressed.
Cancel is an "Action Verb". ActionExpression(s) represent and communicate data management
instructions. The data entities being managed are represented as elements of the OrganizationChart noun in the BOD instance.
The Cancel verb is used when the sender of the BOD is not the owner of the
data, but is sending a request for the document to be canceled.
(Defined in file CancelOrganizationChart.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. | ||