Import Libraries

This will show you how to setup so that you can request and import libraries of ready-made mappings from Golden EDI Cloud.

Finding Message Settings

To setup your system to request and import mappings from our cloud you need to add settings that tell the system how to do it.

Start by searching for the 'GEDI Message Settings' page and open it.

Searching for the message settings page

Adding message settings

You're going to add a few lines to this list to tell it how to request mappings/libraries and how to import them. You do that by creating a new line with the profile that is connected to Golden EDI Cloud, the code for the message and the selected mapping that is used to handle that message.

You can find a list of existing message codes by checking the GEDI message codes page. You can also add your own there if you need.

A mapping "maps" a table to or from our internal message format. This feature makes it possible to export or import any information from any table without writing any code.

To setup import of mappings and mapping libraries we need to add the messages listed in the table below.

Message	Mapping
902
903	LIBRARYREQUEST
904	IMPORTLIBRARY
905
906	MAPPINGREQUEST
907	IMPORTMAPPING

Should look something like this when done

Request Standard Library

We can now go a head and request one of the standard libraries. We are going to request the LTD-STD library to start since it has some basic mappings usable in most setups. To do this we go to the page called 'GEDI library list'.

GEDI library list is where we can import libraries and mappings

Next step is to click on LTD-STD to open up that library so we can request it.

List of libraries currently available for import

Fill in the GEDI-Profile field so it points to your profile that is connected to Golden EDI Cloud. The profile selected here is the one used when requested the library from Golden EDI Cloud.

Now we can request the library by clicking on 'Actions > Request mapping library'. This creates a line in the message queue letting the system know that we want to request the 'LTD-STD' mapping.

The message queue is where the job queue looks for messages to process. All messages ends up here with their content written to the GEDI message lines table.

Requesting a library mapping

Processing the request

Now that we have made the system aware that we want to create an request for a specific library we have to go and manually process it. This is done in the 'GEDI message queue' page so lets go there now.

Searching for the message queue.

When we are in there we can see one lines with message code '903', which is the message that create the actual request readable by the cloud service.

A message going out from your system usually goes through two phases. It starts by creating a message that lets the system know that we want to do something. The second is the message that is created after the first message is run. This second message is created by the mapping system and contains all the data that needs to go out in a form readable by the cloud service. This second message is then read by the cloud service so it can take the action it needs to deliver the message to where you want it to go.

This list contains all messages that are process by Golden EDI

We now manually process this message by click on 'GEDI queue handler run marked line' under 'Process' menu. This will process only the line that you are standing on, you can otherwise use the 'GEDI queue handler all automatic lines' to run all lines.

This is later automated by setting up a job queue. That job will process all messages at the selected interval.

You can reset the message and open it up to be processed again by clicking on 'Reset for new run'

Clicking on 'Remove all transactions' will remove all transactions no matter if they are processed or not. You can instead use the 'Remove all transactions older than 7 days' or even better is to set up a job queue that runs the delete process. That way you can decide which message gets removed and how old they should be.

Now we can see that there is a line with code '903' in the queue which is the message that is going to be read by the cloud service. You can see if it has been read by checking if 'Message Received' is checked or not.

The message received checkbox is checked for both incoming and outgoing messages.

Both our message in the list

If we refresh the page after a few seconds we can see that the cloud service has written down a message with code '904'. This is the content of the LTD-STD library so we can request any one of these mapping or all of them. We wait until the 'message received' checkbox is checked after which we can safely click on 'GEDI Queue handler run marked line' to import the library.

Import the library

Now we have successfully imported a library into our system.