DataArea
Is where the information that the BOD message carries is provided, in this case SyncEmployeeWorkSchedule. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (EmployeeWorkSchedule).
See http://www.openapplications.org/oagis/9.
Element information
Namespace: http://www.openapplications.org/oagis/9
Schema document: org_openapplications_oagis/9_4_1/Developer/BODs/SyncEmployeeWorkSchedule.xsd
Other elements with the same name: DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea, DataArea
Type: SyncEmployeeWorkScheduleDataAreaType
Properties: Local, Qualified
Content
- Sequence
[1..1]
- Sync [1..1] The Sync verb 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 SyncBOD 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.
- EmployeeWorkSchedule [1..*] Represents data related to the planned work hours for an employee. A work schedule typically includes relatively static employee information, such as employee ID and name. It will also include schedule-specific information such as dates and amount of time to be worked.
Attributes
None
Used in
- Type SyncEmployeeWorkScheduleType (Element SyncEmployeeWorkSchedule)
Sample instance
<DataArea> <Sync> <ActionCriteria> <ActionExpression actionCode="Add">token</ActionExpression> <ChangeStatus>... </ChangeStatus> </ActionCriteria> </Sync> <EmployeeWorkSchedule> <DocumentID> <ID>normalizedString</ID> <RevisionID>normalizedString</RevisionID> <VariationID>normalizedString</VariationID> </DocumentID> <AlternateDocumentID> <ID>normalizedString</ID> <RevisionID>normalizedString</RevisionID> <VariationID>normalizedString</VariationID> </AlternateDocumentID> <LastModificationDateTime>2000-01-01</LastModificationDateTime> <DocumentDateTime>2000-01-01</DocumentDateTime> <Description>string</Description> <Note>string</Note> <DocumentReference> <DocumentID>... </DocumentID> <AlternateDocumentID>... </AlternateDocumentID> <DocumentDateTime>2000-01-01</DocumentDateTime> <Description>string</Description> <Note>string</Note> <StatusCode>normalizedString</StatusCode> <Status>... </Status> <LineNumber>normalizedString</LineNumber> <ItemIDs>... </ItemIDs> <Facility>... </Facility> <SerializedLot>... </SerializedLot> <SalesOrderReference>... </SalesOrderReference> <PurchaseOrderReference>... </PurchaseOrderReference> <GroupName>string</GroupName> <SequenceCode>normalizedString</SequenceCode> <StepID>normalizedString</StepID> <StepType>normalizedString</StepType> <IssuingParty>... </IssuingParty> <OperationReference>... </OperationReference> <ReleaseNumber>normalizedString</ReleaseNumber> <ScheduleLineNumber>normalizedString</ScheduleLineNumber> <SubLineNumber>normalizedString</SubLineNumber> <ShipUnitReference>... </ShipUnitReference> <EffectiveTimePeriod>... </EffectiveTimePeriod> <Item>... </Item> <ID>normalizedString</ID> <SealID>normalizedString</SealID> <Type>normalizedString</Type> <FreightItemID>normalizedString</FreightItemID> <ShippingTrackingID>normalizedString</ShippingTrackingID> <Quantity>1.0</Quantity> <UserArea> <!--any element--> </UserArea> </DocumentReference> <Attachment> <EmbeddedData mimeCode="normalizedString">GpM7</EmbeddedData> <URI>http://www.example.com/</URI> <ISBN>normalizedString</ISBN> <FileName>string</FileName> <DocumentDateTime>2000-01-01</DocumentDateTime> <Description>string</Description> <Note>string</Note> <FileType>normalizedString</FileType> <FileSizeQuantity>1.0</FileSizeQuantity> <Title>string</Title> <UserArea> <!--any element--> </UserArea> </Attachment> <Employee> <ID>normalizedString</ID> <Name>string</Name> <Description>string</Description> <GenderCode>Male</GenderCode> <MaritalStatusCode>Divorced</MaritalStatusCode> <BirthDateTime>2000-01-01</BirthDateTime> <DeathDateTime>2000-01-01</DeathDateTime> <AgeMeasure unitCode="normalizedString">1.0</AgeMeasure> <LanguageCode>normalizedString</LanguageCode> <NationalityCountryCode>normalizedString</NationalityCountryCode> <Address>... </Address> <Communication>... </Communication> <JobTitle>string</JobTitle> <JobCode>normalizedString</JobCode> <Responsibility>string</Responsibility> <DepartmentID>normalizedString</DepartmentID> <CategoryCodes> </CategoryCodes> <CategoryClassification>... </CategoryClassification> <Qualification>... </Qualification> <Skill>... </Skill> <Status>... </Status> <Classification>... </Classification> <UserArea> <!--any element--> </UserArea> </Employee> <ContractReference> <DocumentID>... </DocumentID> <AlternateDocumentID>... </AlternateDocumentID> <DocumentDateTime>2000-01-01</DocumentDateTime> <Description>string</Description> <Note>string</Note> <StatusCode>normalizedString</StatusCode> <Status>... </Status> <ReleaseNumber>normalizedString</ReleaseNumber> <LineNumber>normalizedString</LineNumber> <ScheduleLineNumber>normalizedString</ScheduleLineNumber> <SubLineNumber>normalizedString</SubLineNumber> <UserArea> <!--any element--> </UserArea> </ContractReference> <AbsenceType>normalizedString</AbsenceType> <OverTimeIndicator>true</OverTimeIndicator> <ScheduleType>normalizedString</ScheduleType> <WageType>normalizedString</WageType> <WageGroupCode>normalizedString</WageGroupCode> <WorkShiftID>normalizedString</WorkShiftID> <WorkLocation> <ID>normalizedString</ID> <Name>string</Name> <Directions>string</Directions> <Coordinate>... </Coordinate> <Address>... </Address> <Description>string</Description> <Note>string</Note> <UserArea> <!--any element--> </UserArea> </WorkLocation> <WorkTimePeriod> <InclusiveIndicator>true</InclusiveIndicator> <StartDateTime>2000-01-01</StartDateTime> <Duration>P1Y2M3DT10H</Duration> </WorkTimePeriod> <GLEntityID>normalizedString</GLEntityID> <UserArea> <!--any element--> </UserArea> </EmployeeWorkSchedule> </DataArea>