Who is this article for?

Users responsible for managing Documents.

Documents module access is required.

Sometimes, you may be assigned a Document that has a Child dependency.

This article explains the expected behaviour when reviewing these Documents in your Inbox.

1. Processing Child Documents

It is expected to only see Document processing buttons (e.g. Review, Release for Review, Approve) for the Parent Document, as Child Documents are processed along with their Parents.

Releasing a Parent Document with a Child Document in the Expired status for approval or review will prompt you to verify the Child Document before proceeding. This is an important step to ensuring accuracy and compliance of Documents on your system.

Cancelling a release of a Parent Document with a Child Document in the Expired status will revert both to the Edit stage.

If a group of users is listed as Reviewers for a Child Document but not a Parent Document, that group of users will see the Documents needing action in their Inbox but not be able to review them since they're dependent.

2. Processing Parent Documents

Only the comments from the Parent Document will appear in the Changes Made field.

Once the Parent Documents are reviewed, they will move from that status in a users' Inbox to an Approved status.

Editing a Parent Document with an Expired status will prompt you to confirm if you'd like to start a revision for the Child Documents too. If any of the Child Documents are not in the Published status, you will see an error.