GroupMember

Information specifying the occurrence of the operations within an OperationGroup.  At least one occurrence of the GroupMember component is required for each occurrence of the OperationGroup component. Except for the request BODs which use the verbs Get and GetList.

See http://www.openapplications.org/oagis/9.

Element information

Content

• Sequence [1..1]
  1. OperationID [0..1]    Is the identifier of a specific operation. Possible examples of use are in the Manufacturing Routing or the Maintenance Order. or WorkINProcessOperation.
  2. OperationName [0..*]    Is the name of the operation.
  3. SequenceCode [0..1]    Identifies the sequence in which the associated entity is to occur with in a given operation, step or business process..
  4. UserArea [0..1]    Allows the user of OAGIS to extend the specification in order to provide additional information that is not captured in OAGIS.This is done by defining the additional information in XML Schema and referencing the new schema in the xml instance document through the use of namespaces. Once this is done the additional information defined there can be carried in the BOD XML instance document.The Open Applications Group will make best efforts to quickly consider all proposed submissions.The USERAREA is always the last element in all components, except where the component has been extended inline.

Attributes

None

Used in

• Type OperationGroupType (Element OperationGroup)

Sample instance

<GroupMember>
   <OperationID>
      <ID>normalizedString</ID>
      <RevisionID>normalizedString</RevisionID>
      <VariationID>normalizedString</VariationID>
   </OperationID>
   <OperationName>string</OperationName>
   <SequenceCode>normalizedString</SequenceCode>
   <UserArea>
      <!--any element-->
   </UserArea>
</GroupMember>