In Atlas, Queues are a powerful feature used to set up a series of processes to run automatically and unattended. You can set up and run queues when you have large amounts of data to query, export, commit, import, or send as email.
Since all affiliates are sharing the same database server and since database maintenance procedures (like transaction log backups) are also routinely scheduled, the MGB Development Office will control job schedules. At each affiliate, members of specific CRM system roles will be able to create processes that could be scheduled, such as Global Changes, and they will be able to add those processes to a queue.
Each affiliate database currently has a Master Queue which runs nightly; it, in turn, runs four distinct queues:
- Other Scheduled Processes
- Constituencies and Classifications
- Solicit Codes
- Donor Smart Fields
Affiliate Administrators can add steps to each of these queues as needed, and queues, along with other business process, can be monitored with the Atlas Dashboard to ensure that performance is acceptable and that jobs run to completion.
Each affiliate database also has a Weekly Maintenance Queue which runs weekly. It runs these Global changes.
- Delete BVDL Staging Data – Daily
- Delete BVDL Staging Data – Future visits
- Delete BVDL Staging Data – all other imports
- Attribute Clean Up
- Populate Missing Currency Types
- Delete Epic test records
- Clear Smart fields included in Donor Smart Field queue
To run a Global Change or populate a Smart Field just once, or to schedule something to run less frequently than each day, create a ticket in Mojo. You can also process Global Changes directly via the user interface, though it is recommended that you try this in a QA environment first.