ApplicationAreaDataArea| Description |
| Used to request a Change of a ObjectivesResult previously communicated to the receiving application or party. ObjectivesResult Contains information about results, against an objective plan (See ObjectivesPlan noun). Essentially, the same information can be communicated within EPMResult, which is a superset of information that can be reported within employee performance reports. ObjectivesResult is offered as a separate noun for integrations that may not involve the broad array of information available within EPMResult. Change is an "Action Verb". ActionExpression(s) represent and communicate data management instructions. Note that there are two implementation patterns: "Full Refresh" and "Delta." Under the Full Refresh pattern, the type of data management instruction (action code: add, update, delete) is ommitted since a full refresh of the noun or other defined scope is implied. Under the Delta pattern, the action code would be specified to be applied to the selected fields presented in the noun portion of the ChangeObjectivesResult BOD. Choice of implementation pattern is something agreed upon by trading partners. |
| Type : ChangeObjectivesResultType |
| Definition |
|
Used to request a Change of a ObjectivesResult previously communicated to the receiving application or party.
ObjectivesResult Contains information about results, against an objective plan (See ObjectivesPlan noun). Essentially, the same information can be communicated within EPMResult, which is a superset of information that can be reported within employee performance reports. ObjectivesResult is offered as a separate noun for integrations that may not involve the broad array of information available within EPMResult.
Change is an "Action Verb". ActionExpression(s) represent and communicate data management
instructions. Note that there are two implementation patterns: "Full Refresh" and "Delta." Under the
Full Refresh pattern, the type of data management instruction (action code: add, update, delete) is ommitted since a
full refresh of the noun or other defined scope is implied. Under the Delta pattern, the action code would be specified
to be applied to the selected fields presented in the noun portion of the ChangeObjectivesResult BOD.
Choice of implementation pattern is something agreed upon by trading partners.
(Defined in file ChangeObjectivesResult.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. In the case of the ChangeObjectivesResult, the verb Change indicates the action to be performed on the noun ObjectivesResult. | ||
| 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. | ||