Custom noun metadata properties file

Specify the identifier of the custom noun and the verbs that are supported. Optionally, you can also add an entry to specify the relation it has with other nouns. In this file, the definition of ‘IDXpath’ is required. Save the file with a name that matches that of the custom noun name, for example, MySampleDocument.xml. Below is a sample file template.

<?xml version="1.0" encoding="utf-8"?>
<NounMetadata xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schema.infor.com/InforOAGIS/2">

<Noun>
  <NounName>MySampleDocument</NounName>
  <NounType>Transactional</NounType>
  <IDXPath>/*/DataArea/MySampleDocument/SampleHeader/DocumentID
  </IDXPath>
  <DescriptionXPath>/*/DataArea/MySampleDocument/SampleHeader/Description
  </DescriptionXPath>
  <StatusXPath>/*/DataArea/MySampleDocument/SampleHeader/Status
  </StatusXPath>
  <DocumentDateTimeXPath>/*/DataArea/MySampleDocument/SampleHeader/DocumentDateTime
 </DocumentDateTimeXPath>
 <SupportedVerbs>
  <SupportedVerb>Acknowledge</SupportedVerb>
  <SupportedVerb>Process</SupportedVerb>
  <SupportedVerb>Sync</SupportedVerb>
  </SupportedVerbs>
</Noun>
<Relation type="Transactional">
  <ToNoun>Shipment</ToNoun>
  <Priority>10</Priority>
  <RelationLabel>My sample document linked to
  shipment</RelationLabel>
  <RelationPaths> <FromNounPath>/*/DataArea/MySampleDocument/SampleHeader/ShipmentID</FromNounPath>
   <ToNounPath>/*/DataArea/Shipment/ShipmentHeader/DocumentID[1]/ID</ToNounPath>
  </RelationPaths>
 </Relation>
</NounMetadata>

Both files must be placed in one folder with a name that matches that of the custom noun name, then compressed into a .zip file before uploading to IGFC.