# Job Queue Entries

## Introduction

In 'Job Queue Entries' scheduled jobs to automatically process 'GEDI Messages' are configured.&#x20;

The 'Job Queue Entries' page view present a list with current 'Job Queue Entries' with information about what object to run, how often, the current status etc. &#x20;

![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2F462NJhnb7q4y1w5SDTQe%2Fimage.png?alt=media\&token=c064fc88-9ca7-443a-9a4f-f93996a8aba7)

## Extras

{% hint style="info" %}
More information on this subject can be found in our [Core Concepts/'Job Queue Entries'.](https://app.gitbook.com/s/CnajZpb6jyP8d1VA5elK/concepts/jobb-queue-entries)&#x20;
{% endhint %}

## Configure Job Queue Entries

### Instructions

There are three different main 'Job Queue Entries' that usually needs to be configured. \
Each queue settings are depending on the EDI-flows specific needs and the settings below are just examples.&#x20;

1. **GEDIQUEUE**: will be set on a 5min schedule, each workday between 07:00 & 20:00, and will process all new messages to the Cloud Service
2. **GEDIDHEART**: will be set on a 5min schedule, each workday between 20:01 & 20:30, and will check that the communication with Cloud Integration Platform is up and running. &#x20;
3. **GEDIDELETE**: will be set on a once a day schedule, at 04:00, and will clean up old GEDI data no longer needed.

{% hint style="danger" %}
If you have multiple Golden EDI solutions combined in your Business Central Company, and you already have Job Queue Entries configured, you don't need to create new identical ones!\
e.g. if 'GEDIDELETE' already exist, don't create another one.
{% endhint %}

* In Business Central, search and go to the page 'Job Queue Entries'

#### GEDIQUEUE - Job Queue Entry Card&#x20;

* Click new to create a new 'Job Queue Entry Card'.

![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2Fz6ao9mt9lBsDT1MazGek%2Fimage.png?alt=media\&token=ae5b6af7-7948-43eb-b7ef-85ef304d7cf0)

* To the right of the 'General' Section, click 'Show more' to make sure you see all needed fields.

![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FsBhz5xJIsxNDe0fdiToL%2Fimage.png?alt=media\&token=54720d75-051d-4abf-ad99-30cfef9e8341)

* Fill in the 'Job Queue Entry Card' for 'GEDIQUEUE' as per screenshot or list below.

![](https://firebasestorage.googleapis.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2ldF5Ogu5xZEyXimzB%2Fuploads%2FDST0lNcNLwwM8LBBWdq1%2Ffile.jpeg?alt=media)

#### General Section:

| Field                   | Value         |
| ----------------------- | ------------- |
| Object Type to Run      | **Codeunit**  |
| Object ID to Run        | **70019001**  |
| Job Queue Category Code | **GEDIQUEUE** |

#### Recurrence Section:

| Field                       | Value   |
| --------------------------- | ------- |
| Run on Mondays              | Checked |
| Run on Tuesdays             | Checked |
| Run on Wednesdays           | Checked |
| Run on Thursdays            | Checked |
| Run on Fridays              | Checked |
| Starting Time               | 0700    |
| Ending Time                 | 2000    |
| No. Of Minutes between Runs | 5       |

* The 'GEDIQUEUE' 'Job Queue Entry' is now setup to processing the EDI messages automatically every 5min, each workday between 07:00 and 20:00
* Close the Pop-up and **don't set the job queue to ready yet.**

#### GEDIHEART - Job Queue Entry Card&#x20;

* Click new to create a new 'Job Queue Entry Card'

![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FRyHSh82MJhzWNy4xbffq%2Fimage.png?alt=media\&token=cd10b5c7-38bd-487f-8cb9-2cb35bce8bb0)

* To the right of the 'General' Section, click 'Show more' to make sure you see all needed fields.

![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FsBhz5xJIsxNDe0fdiToL%2Fimage.png?alt=media\&token=54720d75-051d-4abf-ad99-30cfef9e8341)

* Fill in the 'Job Queue Entry Card' for 'GEDIHEART' as per screenshot or list below.

![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FDk16iM9V9QAlHHuTW5Gv%2Fimage.png?alt=media\&token=1d2b2902-d651-4c0c-9648-eb987c27e5eb)

#### General Section:

| Field                   | Value         |
| ----------------------- | ------------- |
| Object Type to Run      | **Codeunit**  |
| Object ID to Run        | **70019001**  |
| Job Queue Category Code | **GEDIHEART** |

#### Recurrence Section:

| Field                       | Value   |
| --------------------------- | ------- |
| Run on Mondays              | Checked |
| Run on Tuesdays             | Checked |
| Run on Wednesdays           | Checked |
| Run on Thursdays            | Checked |
| Run on Fridays              | Checked |
| Starting Time               | 2001    |
| Ending Time                 | 2030    |
| No. Of Minutes between Runs | 5       |

* The 'GEDIHEART' 'Job Queue Entry' is now setup to processing the EDI messages automatically every 5min, each workday between 20:01 and 20:30
* Close the Pop-up and **don't set the job queue to ready yet.**

#### GEDIDELETE - Job Queue Entry Card

* Click new to create a new 'Job Queue Entry Card'

![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FUXagSAzphfOos0aTFpRy%2Fimage.png?alt=media\&token=642f36f3-1016-49e3-9ce7-dde1163d72df)

* To the right of the 'General' Section, click 'Show more' to make sure you see all needed fields.

![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FJL1luwKRCxfiYZyels46%2Fimage.png?alt=media\&token=60956fd9-4892-4b80-b179-fdac35bbe4b9)

* Fill in the 'Job Queue Entry Card' for 'GEDIDELETE' as Screenshot or list below.

![](https://firebasestorage.googleapis.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2ldF5Ogu5xZEyXimzB%2Fuploads%2FjyzTray2N1rVvKuAHtNP%2Ffile.jpeg?alt=media)

#### General Section:

| Field                   | Value          |
| ----------------------- | -------------- |
| Object Type to Run      | **Codeunit**   |
| Object ID to Run        | **70019006**   |
| Job Queue Category Code | **GEDIDELETE** |

#### Recurrence Section:

| Field             | Value   |
| ----------------- | ------- |
| Run on Mondays    | Checked |
| Run on Tuesdays   | Checked |
| Run on Wednesdays | Checked |
| Run on Thursdays  | Checked |
| Run on Fridays    | Checked |
| Starting Time     | 0400    |

* The 'GEDIDELETE' 'Job Queue Entry' is now now setup to clean up old GEDI data no longer used once a day at 04:00.
* Close the Pop-up and **don't set the job queue to ready yet.**

## Start the Job Queue Entries

Once the setup is ready for Go Live the three GEDI-related Job Queue Entries needs to be set to Ready.   &#x20;

### Instructions

* In Business Central search and go to 'Job Queue Entries'

![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FylEpGmbCndR7Hte7fw67%2Fimage.png?alt=media\&token=c123e773-e3c2-4b39-8440-07c3ff037d4e)

* Select the 'Job Queue Entrie' that you like to start and click Set Status to Ready<br>

![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FdwMzegUOhC6t0aNt72CO%2Fimage.png?alt=media\&token=f31ac619-e55d-45e9-b2f3-e339b7282d87)

The status will change to Ready. &#x20;

![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FAFN8BfFAJJzS7nXOGEgG%2Fimage.png?alt=media\&token=a7e89512-7eca-4e72-a903-a595b4b0cae5)

{% hint style="danger" %}
Please note that the user starting the 'Job Queue Entries' needs to have permission set to proper rights to be able to run the job. This is due to that the user starting the job queue is actually performing all the actions inside Business Central. E.g. sending e-mail, creating order etc.&#x20;
{% endhint %}

{% hint style="danger" %}
After setting the status to Ready check that Earliest Start Date/Time is in the future else it will run as expected. &#x20;
{% endhint %}

## Next Step

Next Step is to learn how to manage the 'GEDI Message Queue'.
