-
Notifications
You must be signed in to change notification settings - Fork 19
System Admin UI
Matt Roth edited this page Jan 10, 2023
·
9 revisions
A system admin page exists within Caseflow. This page can be accessed by System Admin Users only. The purpose of this page is initially created so that System Admin users can generate an extract which contains information on veteran updates that will be sent to MPI.
Simply go to /admin
OR when in /test/users
, click on the Miscellaneous tab and then click Admin
The system admin page will contain a button labeled Extract Veterans for MPI
.
Once this button is clicked:
- A System Admin Event is created
- A SQL command will be run to gather data for the extract.
-
Note: The most recent System Admin Event that was completed will be compared to the
STADTIME
field in the CORRES table so that only veterans added since are included in the extract.
-
Note: The most recent System Admin Event that was completed will be compared to the
- Two scenarios can happen here:
- If the Extract SQL is successful:
-
completed_at
will be set to the timestamp of when the SQL successfully ran -
info
will be set to the number of veterans that were found from the SQL statement
-
- If an error occurs during the Extract SQL:
-
errored_at
will be set to the timestamp of when error occurred.
-
- If the Extract SQL is successful:
- Once the System Admin Event is updated:
- If number of veterans within
info
is not 0, then return data for CSV. - If number of veterans within
info
is 0, return a message stating no new veterans.
- If number of veterans within
- sys_admin_page
- A feature toggle that when enables the system admin page to load when enabled.
- vet_extract_timestamp
- Disabling this disables the check against system_admin_event table when looking for veterans for the extract
- vet_extract_pipe_delimited
- When enabled swaps to pipe delimitation for the CSV
- comma is the default
- Home
- Acronyms and Glossary
- Caseflow products
- Caseflow Intake
- Caseflow Queue
- Appeals Consumer
- Caseflow Reader
- Caseflow eFolder
- Caseflow Hearings
- Caseflow Certification
- Caseflow APIs
- Appeal Status API
- Caseflow Dispatch
-
CSUM Roles
- System Admin
- VHA Team Management
- Active Record Queries Resource
- External Integrations
- Caseflow Demo
- Caseflow ProdTest
- Background
- Stuck Jobs
- VA Notify
-
Caseflow-Team
- Tier 4
- Bat Team
- Technical Documentation
- Backend Code Patterns
- Backend Working Group
- FACOLS, VACOLS DB Schema
- Asyncable Models
- External Data: where and why
- Data Fetching Scripts
- Caseflow Data Model and Dictionary
- User Access Permissions
- Controller Schemas
- Constants
- Frontend Best Practices
- Accessibility
- How-To
- Debugging Tips
- Adding a Feature Flag with FeatureToggle
- Editing AMA issues
- Editing a decision review
- Fixing task trees
- Investigating and diagnosing issues
- Data and Metric Request Workflow
- Exporting and Importing Appeals
- Explain page for Appeals
- Record associations and Foreign Keys
- Upgrading Ruby
- Stuck Appeals
- Testing Action Mailer Messages Locally
- Re-running Seed Files
- Rake Generator for Legacy Appeals
- Manually running Scheduled Jobs
- System Admin UI
- Caseflow Makefile
- Upgrading Postgresql from v11.7 to v14.8 Locally
- VACOLS VM Trigger Fix M1
- Using SlackService to Send a Job Alert
- Technical Talks