---
title: "Post release staging journals"
slug: "post-release-staging-journals-1"
tags: ["Task", "PLM"]
updated: 2026-07-21T07:55:01Z
published: 2026-07-21T07:55:01Z
canonical: "docs.staedean.com/post-release-staging-journals-1"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Post release staging journals

Use the **Staging journal posting engine** to post open release staging journals. You can configure parallel processing, limit the number of release structure levels to process, transfer failed lines to an error journal, and run the posting as a batch job.

## Steps

1. Go to **Modules > Engineering change management > Periodic > PLM Integration > Post release staging journals**.
2. In the **Staging journal posting engine** dialog, expand **Records to include**.
3. Select **Filter** and confirm the following criteria:
  - **Scenario**: **Import release**
  - **Journal status**: **Open**
4. Under **Posting helpers**, configure the following options:
  - **Number of threads**: Enter the number of threads to use for posting. Increase the value when parallel processing is required.
  - **Transfer failed lines**:
    - Set to **Yes** to post valid lines and move failed lines to a separate error journal.
    - Set to **No** to stop the posting when a validation error occurs.
  - **Max levels**: Enter the maximum number of release structure levels to process. Use **0** when no level limit is required.
5. Under **Run in the background**, configure the batch options when required:
  - **Batch processing**: Set to **Yes** to run the posting as a batch job.

> [!NOTE]
> Note
> 
> The below fields apply only when **Batch processing** is set to **Yes**.
  - **Task description**: Review or update the batch task description.
  - **Batch group**: Select the batch group that will process the job.
  - **Private**: Set to **Yes** to make the batch job visible only to you.
  - **Critical job**: Set to **Yes** if the batch job must be treated as critical.
  - **Monitoring category**: Select a category for monitoring the batch job.
  - **Recurrence**: Define how often the batch job should run.
  - **Alerts**: Configure notifications for the batch job.
  - **Start date**: Review the date, time, and time zone when the batch job will start.
6. Select **OK** to start the posting process.
7. The system validates the release staging journal data and posts the valid entries to the Dynamics 365 product master tables.
8. Review the Infolog message and journal status after posting.

### Posting results

The posting can have one of the following results:

- **Successful**: All lines are posted, and the journal status changes to **Posted**.
- **Partially successful**: Valid lines are posted, and failed lines are moved to an error journal. The source journal status changes to **Posted with errors transferred**.
- **Failed validation**: No valid lines are posted. When **Transfer failed lines** is set to **Yes**, the failed lines are moved to an error journal.
- **System error**: An unexpected system, database, or infrastructure error stops the entire posting process. Failed lines are not transferred.