"'GEDI Messages' is usually configured to be automatically processed by 'Job Queue Entries'"
'GEDI Messages' is usually configured to be automatically processed by 'Job Queue Entries'. 'Job Queue Entries' are configured to call on specific Code Units and 'Job Queue Category Codes'.
'Job Queue Category Codes' are then configured against an event and 'GEDI Message Code' in the 'GEDI Message Selection'.
There are some standard 'Job Queue Entries' that many 'GEDI Setups' relies on, for example the 'Job Queue Category Code' 'GEDIQUEUE'. Additional 'Job Queue Categories' can be configured if certain 'GEDI Messages' should be processed on other time interval than 'GEDIQUEUE'.
The CIP has the possiblity to track if the 'Job Queue Entries' are still running as expected. This functionality is called a 'GEDI Heartbeat'. If the 'Job Queue Entry' for some reason should stop running, the CIP can send out notifications about 'GEDI Heartbeat' failure.
There can also be other GEDI related Code Units that 'Job Queue Entries' could call upon. For example, when configuring an automatic master data sync, a 'Job Queue Entry' defines how often the sync should run.
Another 'Job Queue Entry' that should be configured in most Standard App installations is the 'Job Queue Category Code' 'GEDIDELETE'. 'GEDIDELETE' is a clean up job that deletes old 'GEDI Messages' depending on a setting in the 'GEDI Message Code'. This job is most often run once a day making sure that 'GEDI Messages' doesn't store too much information over time.
