Managing review queues
A Policy Manager review queue is one or a group of users to assigned to handle the review, approval, or other actions. Every person in the review queue will receive a review notification but only one person takes ownership.
A user cannot be assigned to a task. A review queue with at least one user is assigned to a task and a member of the review queue must take ownership of a task to complete the task. The owner of the task may release ownership for another user in the queue to assume ownership.
You must set up a review queue before the queue can be added to a review task.
可用的审阅周期操作
审阅周期操作因工作流阶段而异，支持协作编辑或基于所有权的任务管理。审阅队列确保在审阅流程的各阶段将相应的工作转派给适任的审阅者。
起草和修订阶段支持协作编辑，允许指定审阅队列成员编辑该文档，而无需承接所有权。
核准、发布和结束阶段遵循基于所有权的模型，其中任务所有权和指派控制机制持续有效。
文档审阅的范围和完整性取决于针对该文档所配置的审阅层级或审阅队列。创建审核队列后，您可以执行以下操作：
完成最终审阅：指派专人或责任群组以完成最终审阅。
协作编辑：在起草和修订阶段，获得授权的审阅队列成员可以协作编辑文档，而无需承接所有权。
承接所有权：在核准、发布和结束阶段，将任务指派给自己进行处理。
释放所有权：在基于所有权的阶段中，释放任务，以便审阅队列中的其他合格用户可以处理该任务。
标记完成：将文档审阅或任务标记为完成。如果多位用户仍在编辑文档，则在编辑完成之前，标记为完成选项可能不可用。
- 添加：选择菜单图标以向文档中添加其他小节或工作流步骤。其他选项包括：
- 添加章节：向文档添加新章节以完成文档审核。
- 添加步骤：向文档中的现有章节添加新步骤。
- 添加编辑：向文档添加额外的编辑组件。
- 添加审批：在完成文档审核周期之前添加额外的审批层级。
- 添加修订：在标记为完成之前，添加额外的层级来修订文档。
- 添加关闭：在将文档标记为完成之前，添加额外的层级进行关闭。
- 插入片段：为您的文档添加可复用的片段。
- 移除：移除您为文档添加的审阅层。
- 恢复：若在审核文档时意外删除了章节或层级，则恢复文档的历史版本。
- 管理前序任务：您可以在完成文档审核周期前分配前序任务。
说明
在起草和修订阶段，如果指派了审阅队列，审阅队列成员便可以协作编辑文档。如果未指派审阅队列，则仅文档所有者或管理员可以编辑该文档。最多 5 位用户可以同时协作编辑同一文档。
Add a review queue
From the left navigation menu, select Administration > Reviews.
In the Review queues tab, select the +Add new review queues .
Complete the information for the queue
Enter a Name for the queue and add a Description.
Select the Type to identify document ownership and task assignment functions for the queue. For example, Compliance may own a document but various review queues, including a compliance review queue, may accept tasks for review.
For Document Ownership Only: Individuals can own a document but will not be involved in reviewing tasks in a review cycle. Use this selection to assign ownership to a stakeholder or group that isn't an active user of Policy Manager. For example, this may be a Board or Committee of the Board that is the owner and primary stakeholder of a document but will never use Policy Manager and, instead, will have another group of users be responsible for document life cycle management.
For Task Assignment Only: Individuals will only be assigned tasks and can take ownership of a task. Individuals in the queue do not own the document.
Available for Both: The queue owns the document and can be involved in task actions.
- Select Active for the queue to be made available immediately. If a queue is active, it cannot be deactivated if it is used in one or more flows.
Select a Flow Definition (a Review Flow). For more information, see Managing review flows and tasks.
Select Next.
Add or remove uses from the queue, as needed:
To add users to the queue, search for the user in All Other Users. Select the Action
button for the user. The user moves to Current Users.- To remove users to the queue, search for the user in Current Users. Select the Action button for the user. The user moves to All Other Users.
Select Save to create a new review queue.
Manage a review queue
From the left navigation menu, select Administration > Reviews.
Select any of the following from the Actions column:
Edit review queue to update the information.
To add users to the queue, search for the user in All Other Users. Select the Action
button for the user. The user moves to Current Users.- To remove users to the queue, search for the user in Current Users. Select the Action button for the user. The user moves to All Other Users.
If Active is selected, the review queue is available for task assignment. You can deselect Active. The system will not allow you to inactivate a review queue that is currently in active use.
Clone to create a duplicate or clone the review queue. You can edit the cloned review queue to make a new review queue.
Delete to permanently remove the review queue. The system will not allow you to inactivate a review queue that is currently in active use.
