-
Notifications
You must be signed in to change notification settings - Fork 2
Description
Add text to the Metadata page directing the user to the GitBook File Storage page where the metadata file resides so states can pull the file and manually process the metadata.
1st suggestion for text: The Metadata Update failed. To retrieve the metadata file and manually process it, navigate to the File Storage page in GitBook.
Acceptance Criteria
Setup:
The new page must exist in GitBook.
The tester needs access to GitBook.
The Generate UI needs to be set so that the metadata update fails causing the message to display.
QA:
Testing proof: add a screenshot of the page that passed testing to the ticket as the work is completed.
Migration Steps:
Ex.) RDS - App.Wrapper_Migrate_Membership_to_RDS
Ex.) Reports - 052
Test Cases: does this require an update to the test case(s)? Y/N:
Documentation - does this require an update to documentation (GitBook edits)? Yes
Release Notes? [Add language for Release Notes here…]
OSC Impact - does any part of this task require an OSC ticket? Yes - #834
If yes, once the OSC ticket is created, add the OSC ticket # to the JIRA ticket.
ETL Checklist Impact - does any part of this task require an update to the ETL Checklist (i.e., were changes made to the database tables or columns)? No