-
Part is created in HxGN EAM.
-
EAM publishes SyncItemMaster bod.
-
Convert the SyncItemMaster to SyncEnvelope using a mapper or an XSLT.
-
SyncEnvelope bod which has a GetParts soap request will be used as input document and Consume the SyncEnvelope from the shared folder via a File Connector without using a mapper
You can you <IonApiRef> tag if you want to give dynamic input from the ItemMaster to the SyncEnvelope custom bod.
For more information on <IonApiRef> see the Infor ION® Technology Connectors Administrative Guide.
-
The ION API will make a service call to EAM and receive the response as AnyDocument (Response XML).
-
The file connector will write the response to a share folder.
-
Once all the configurations are done, activate the flow and create a part in EAM or create a SyncEnvelope Bod and place in a share folder for the file connector to pick.
-
On successful execution of the document flow you should be able to see a Response xml as Any Document with GetPartResults information.
The possible ways in which you can make a request to ION API using the ION API Document handle the response.
-
Use the Input document as AnyDocument and process the Output Response of the ION API call to AnyDocument where you will place the soap EAM request with <MP0241_Getpart_001> as part of the AnyDocument as shown here.
-
Use the Input document as Custom bod like SyncEnvelope and process the Output Response of the ION Api call to AnyDocument.
For more information on custom bods please see the Infor ION® Desk User Guide.
-
Use the Input document as a standard bod like SyncItemMaster and Map the bod to a SyncEnvelope Custom bod or a AnyDocument type and process the Output Response of the ION Api call to AnyDocument or some supported format.
-
Input AnyDocument is attached in the Attachments pane.
