Consolidate reviews and prepare to issue - HxGN SDx - Update 64 - Help

A consolidator can complete the consolidation step even without any review completed. The consolidator compiles all the document reviews, comments, and actions as part of the document review consolidation workflow step.

The consolidator responds to each document review, either with approval or by creating a sub-review as an internal technical query asking for further information. These appear in the document reviewers To Do List for rectification. The consolidator can reject or terminate any duplicate or inappropriate actions.

The consolidator creates the consolidated review, which contains a marked-up PDF rendition file with all applicable actions. Finally, the consolidator sets the return code on the document before clicking COMPLETE to finish, which places the consolidated document on a workflow to the recipient contractor.

The consolidator can:

• Determine how a review proceeds by either:

  • Rejecting the review and sending any rejected actions back to the reviewer for rework.

    For any rejected actions, the state of the review and actions are set to DRAFT REJECTED. If the rejected actions are associated with a markup layer and that layer is selected to return to the contractor, warnings are given that the selected layer contains unapproved actions. The consolidator cannot complete the process to issue the document reviews to the contractor until the action is resolved, deleted, or moved to a markup layer that is not selected to return to the contractor.

  • Completing the consolidation of reviews, actions and comments and issuing them to the contractor.

  • Add one or more users as document reviewers during the review process.

    

    • When a consolidator adds a user, who has a document receipt notification step, as a reviewer, the document receipt notification step is replaced by a review step.

    • The new review step is assigned the same target date as that of the original step. If the review is already overdue, the added reviewer will receive an overdue step.

• View and edit any reviews, actions, and comments in a DRAFT or RESERVED state, prior to submission for contract compliance review.

• View all supporting documentation for every review, action, or comment.

• View the markup layers and select which markup layers you want to associate with a specific action.

• Make changes to the reviews, actions, or comments and then reconsolidate if a document review is rejected after a contractual compliance review.

• Send technical queries if more information is required on an action or comment.

The QA Append Reviewer workflow handles the request from a consolidator to add one or more reviewers to a document that is in review. The workflow creates a review object for the appended reviewer and adds a task in the user's To Do list.

When a QA review is completed or waived, it reflects in the review progress column as a percentage. The percentage of the progress depends on the number of reviewers to the document. For example, If a document has two reviewers assigned:

Documents can also be marked up by users who are not assigned to a QA review task. The users who create the markups and comments outside the context of QA review are called as contributors.

The reason why a contributor might want to create markups outside of a QA review is to provide general observations that are shared as comments/markups and the markups provided in other context like technical queries or actions context.