This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Request List Notifications
In collaborative projects, multiple documents often need to be requested, reviewed, and submitted by different people. Request List (RL) notifications keep project teams informed and organized by alerting users to new requests, upcoming deadlines, and status changes.
This ensures that all Request List updates are on track, avoid missed tasks, and creates seamless collaboration—making document management easier and more reliable for all stakeholders.
Key capabilities
| Sl. No. | Notification | Recipient(s) | Description | Channel(s) | Frequency | Notification Location |
|---|---|---|---|---|---|---|
| 1 | RL Activated | Assignee | Informs the Assignee that a new RL is assigned so they can understand their so they know what documents are needed and can begin preparing them. | Once | RL | |
| 2 | RL Activated | Reviewer | Notifies reviewers that a RL has been created, allowing passive visibility into its progress. | In-app | — | RL |
| 3 | RL Activated (Duplicate) | Assignee | Same as above — ensures assignee is aware of the new RL and can begin planning. | Once | RL | |
| 4 | Due Date Reminders | Assignee | Reminds users of upcoming deadlines to help prioritize and complete tasks on time. | Email & In-app | 10, 5, 3, 1 days before; weekly after due | RL |
| 5 | Item Assigned | Assignee | Informs the user that a specific Request List item has been assigned and requires action. | Email & In-app | Once | Item |
| 6 | RL Closed | All stakeholders except closer | Indicates that the RL is no longer active, helping users clean up or disregard outdated items. | Once | RL | |
| 7 | RL Lifecycle Change (Delete/Freeze/Restore) | All stakeholders except actor | Communicate to users that there is a change in RL status (e.g., deleted, frozen, restored) so users stay informed of availability. | Once | None | |
| 8 | RL Restored (Future Due Date) | Assignee | Reinstates due date reminders for restored RLs, ensuring users are re-alerted to upcoming deadlines. | Email & In-app | — | RL |
| 9 | RL Reopened | All stakeholders except actor | Notifies users that a previously closed RL is active again and may require renewed attention. | Once | RL | |
| 10 | RL Reopened + Due Date Reminders | Assignee | Combines reopening notice with deadline reminders to help users resume work and meet due dates. | Email & In-app | — | RL |
| 11 | RL Item Rejected / Reopened | Assignee | Alerts user that a task needs revision or rework, prompting them to upload a corrected file. | Once | RL | |
| 12 | New To-Do Added | Assignee | Notifies the user of newly assigned tasks so they can begin work and manage workload. | Once | To-Do | |
| 13 | New To-Do + Due Date Reminders | Assignee | Same as #12, with added reminders to help users stay on track with deadlines. | Email & In-app | 10, 5, 3, 1 days before; weekly after due | To-Do |
| 14 | All Items Submitted | Reviewer or RL owner | Indicates that all tasks are complete and ready for review, enabling timely feedback or approval. | Once | RL | |
| 15 | RL Item(s) Submitted | Reviewer | Indicates that a file has been uploaded and is ready for review, enabling timely feedback or approval | Once, one-hour time-frame digest | RL |
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.