ASR - Scrub File Monitoring

[BaharF]

ASR has file monitoring for Scrubs. Using "Contributory Build File Ingest Movement on LZs on ASR" find out what is offered currently and if this is a feature we need to implement in Tombolo.

For any questions regarding this please contact Rapunzel Castro.

This document has detailed documentation on Scrub Queue Monitoring - https://reedelsevier.sharepoint.com/:w:/r/sites/OG-InsuranceDataEngineering/_layouts/15/Doc.aspx?sourcedoc=%7B5B2A731E-DCF8-4882-9FD0-EE250AE33A16%7D&file=Activity%20Summary%20Report%20(ASR).docx&action=default&mobileredirect=true&DefaultItemOpen=1&wdOrigin=TEAMS-MAGLEV.p2p_ns.rwc&wdExp=TEAMS-TREATMENT&wdhostclicktime=1712071457421&web=1

Wireframe -

Scrub Queue monitoring is essentially monitoring a directory to ensure that files do not stay in place for too long as the proceed through a workflow. We will be creating a general user "directory monitoring", which will give users the ability to monitor directories for files standing in place for too long. We will then add in ASR specific flags if the integration is turned on. In the future we can add additional monitoring options such as file limit (notify if too many files exist in directory), total size (notify if sum of file sizes is too large), and more.

Migrations - Add Directory Monitoring with the following columns

1. id
2. app id
3. cluster_id
4. name
5. cron
6. type
7. active
8. directory
9. metaData
10. approved
11. approvalNote
12. approvedBy
13. created
14. updated
15. deleted

backend Routes + unit tests -

1. We will need a new set of routes for directory monitoring. Create, update, delete, fetch one, fetch all, approve

2. Job for running the monitoring and sending out notifications

3. Notification template for general users, and Notification Template for ASR users

4. Route to fetch all subdirectories for directory Browser

Front End Functionality

1. Create new Directory monitoring page

2. Create new Directory creation modal

3. Create Approval process

4. If ASR integration is on, turn on extra fields

Sub Tasks and Time estimations
Migrations - 1 day
Backend Routes and Unit Tests - 3-5 days
Job Creation for Monitoring - 3-5 days
Notification Templates - 1-3 Days
Front End, General User - 10-15 Days
Front End, ASR Additions - 3-5 Days

• ASR - Scrub File Monitoring - Migrations #729
• ASR - Scrub File Monitoring - Backend Routes and Unit Tests #730
• ASR - Scrub File Monitoring - Job Creation for Monitoring #731
• ASR - Scrub File Monitoring - Notification Templates #732
• ASR - Scrub File Monitoring - Front End, General User #733
• ASR - Scrub File Monitoring - Front End, ASR Additions #734