Test Account Data Refresh
This document explains how users can set the test account to refresh from the production/live system. This will not affect the existing data in the live data account, but it will override the data in the test account since it is replaced with the live system data (with the exception of the data defined below). Once selected, the data will refresh overnight during your regular nightly maintenance window. If your test and live accounts are not on the same software version, this process will replace the software version on test with the version that is currently on Live. So, if you plan to test a new software version, but with fresh data from Live, you should first copy over the data and then set the upgrade flag on the test account.
Overview
To facilitate system and data testing you have access to both a production/live account and a test/sandbox account. We strongly recommend that any large changes or data imports are first implemented in the test system and verified prior to processing in the live account.
You can update the data in the test account by refreshing test from live. This will occur overnight during the system maintenance. The test system data will be completely erased and replaced with the data in your live system (with the below exceptions).
System maintenance starts after midnight in your server time zone, and during the maintenance routine you will not be able to access your system. Maintenance runs on the live account first and an hour later maintenance runs on TEST, it is during this second process that the test refresh occurs.
Test Account Refresh
Navigate to the Systems Settings module in Naviga and click on the Setup menu -> Test Account Data Refresh.
In the option Test Account Set to Auto Refresh, you can click the “Yes” option. This means that the test account software version will be overwritten with the latest Live version during the maintenance time period mentioned above.
After it runs according to the nightly schedule, this flag will automatically set itself to “No” as the copy has occurred. To repeat the process, user must change this option back to “Yes” for the next refresh.
The next option “Email when Refresh is Completed” allows you to enter one or more email addresses of recipients you want to receive an email notification when the test account is refreshed successfully.
The next 3 fields are for information only and are automatically filled in after the refresh is complete.
Auto-Refresh Last Set by User: This is the user ID who set the auto refresh last.
Last Test Account Refresh Date / Time: This gives you the date and time stamps of when the test account was last refreshed.
Messages: This provides any messages from the system during the refresh process.
When finished, click on the “Save” button to store these settings.
Items Not Overwritten
The following items will retain Their Original Values. They are client-facing fields and screens which are saved off before the refresh and then copied back into place after the refresh. Naviga Personnel - See Internal Documentation for additional, back end/non-client-facing fields
CONNECTION SETUP AND CUSTOM FIELDS
INVOICE SETTINGS -> OVERRIDE EMAIL TO ADDRESS
INVOICE FORMS -> OVERRIDE EMAIL TO ADDRESS Import Currency Rates FTP section -> Folder path
color selection from the 
dropdown in the menu
Enable EHF Integration flag
Test API Users
Naviga Parameters
Navigate to System Settings -> Setup -> Naviga Parameters. All the fields on this screen will not be copied over from PROD into TEST.
Auto-Import A/R Payments
Navigate to A/R Module -> Setup -> Auto Import of A/R Payments (both sub-menus). These settings will not be copied over from PROD into TEST.
Phantom Scheduler Process Queue
Navigate to System Settings -> Setup -> Phantom Scheduler. This will not be copied from PROD to TEST
Material Preflight settings
Prior to 2023.2, this was found on the Portal Setup, and only the Preflight section was saved off and then copied back in during a data refresh. It is now it's own screen and is used by both internal users and portal users, so this entire screen will be retained in a data refresh.
Salesforce Setup
In the Advertising Module, Navigate to Setup -> Admin -> Salesforce Integration Setup. Setup here will not be copied to Test from PROD.
Ad Server Setup
In the Advertising Module, Navigate to Setup -> Admin -> Ad Server Integration Setup. Along the left navigation tree, the Connection Setup and the Custom Fields nodes are not copied from prod to test. This way, if you have the Interface not enabled in Test, it won't turn on after copying prod to test.
Advertising Setup
Navigate to Advertising Module -> Setup -> Admin -> System Parameters. The Override email to address is a field that typically will be set to an internal address for testing, but you would not want to set that in a production environment or your clients wouldn't receive their invoices. The other fields on this screen ARE copied from PROD to Test, but not this one field.
A/R System Parameters
Navigate to A/R Module -> Setup -> Admin -> A/R System Setup. Similar to above setting, but this would be for Misc. A/R Invoices. Typically this is only set in a test environment, so that is the only field on the A/R Parameters that is not copied from PROD to TEST
Also, in the section for Importing Currency Rates via FTP, the Folder Path will not be copied over in a refresh so that test can point to a test path and prod can point to a prod path.
Credit Card Data
Credit cards are not copied over from live into the test system. Generally it is not desired to charge a client's credit card from the test system, so to prevent mistakes, we do not copy credit cards over. If you need to test something with a credit card, you will need to enter in the card number (or a test card number provided by your processor) into the test system.
Affidavit Automation
Navigate to Billing -> Affidavits -> Affidavit Automation. Affidavits can be printed and / or emailed to clients. Because of the emailing of affidavits, we do not copy over the Affidavit Automation setup when the test system is refreshed with the live so that the clients don't end up getting duplicates, or emails about affidavits which were later cancelled in live, etc.
System Color Choice
The system defaults to the Catalina Blue selection (shown below), but the user can select from the other choices on the list. To more easily differentiate between TEST and PROD, some users like to choose different colors between the two databases. Prior to 24.3, when test was refreshed, whatever color choice was used in PROD would be copied over to TEST and the user would need to re-pick their test color choice. Now, the color choice sticks and will not be reverted back to the PROD color during a refresh.
EHF Integration Flag
This flag can be found in Advertising Module, Setup -> Admin -> Other Integrations
The flag to enable the EHF Integration will not be copied to test from Prod in the Test Account Data Refresh Process.
Testing API Users
When copying Prod to Test, the Prod API users will be copied over, but any users that were created in test will not be overwritten.
Last updated
Was this helpful?