RAAMP Sandbox

The Sandbox is a good testing site, but some things it doesn’thas do well.limitations

1. Cache bustingbusting.
   Caching in RAAMP takes placesplace in javacript files as well as images and style sheets, The production version of RAAMP has Cache busting and the ability to destroy all cached elements. The Sandbox does not implement cache busting. If you experience issues especially with new feature, you can try ctrl+f5 and it will hard refresh and replace any cached files. It is helpful if you do mention when a hard refresh is required to Support

2. FilesFiles.
   Only files that were uploaded into Devraampthe Sandbox will be available in Devraamp.the Sandbox. If you try to download a file or image that was accessible in RAAMP it will error out in devraamp.the Sandbox.

3. Emails.
   Emails will be sent out of RAAMP so be careful when testing sharing or emailing. You don’t want to accidently send out emails from devraamp.the Sandbox.

4. Nightly Run Tasks.
   Notifications, Delinquency, and insurance compliance information will not be updated via a nightly job, so if there is missing information it might be because the information is outdated from when it was created in RAAMP during an automated task.

5. Database is not kept in sync.
   DevraampThe Sandbox has a separate database from RAAMP. YOU WILL LOSE YOUR CHANGES IN DEVRAAMPthe Sandbox and any work you have done in devraampThe Sandbox cannot be transferred to RAAMP. AlsoAlso, occasionally I need to test specific users and because of security the passwords will be overwritten so occasionally you will try to log into devraampThe Sandbox, and you will get a lock out notice or a password incorrect notice. You can either send me an email or reset youyour password, just note next time I do a sync your password will revert back to RAAMP’s

6. Signatures.
   E-signatures will not work in The Sandbox

1.Mapping.
Maps and location, Geocoding and Zip code look ups will not work in the Sandbox