You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
id
app id
cluster_id
name
cron
type
active
directory
metaData
approved
approvalNote
approvedBy
created
updated
deleted
backend Routes + unit tests -
We will need a new set of routes for directory monitoring. Create, update, delete, fetch one, fetch all, approve
Job for running the monitoring and sending out notifications
Notification template for general users, and Notification Template for ASR users
Route to fetch all subdirectories for directory Browser
Front End Functionality
Create new Directory monitoring page
Create new Directory creation modal
Create Approval process
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 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
backend Routes + unit tests -
We will need a new set of routes for directory monitoring. Create, update, delete, fetch one, fetch all, approve
Job for running the monitoring and sending out notifications
Notification template for general users, and Notification Template for ASR users
Route to fetch all subdirectories for directory Browser
Front End Functionality
Create new Directory monitoring page
Create new Directory creation modal
Create Approval process
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
The text was updated successfully, but these errors were encountered: