To learn what a Test Environment Refresh (Refresh) is and how to request one, refer to Test Environment Refresh.
Integration options control how integrations and tools are handled during a Refresh.
- If you want a standard Refresh, you do not need to request any options. By default, all Production LTI and extensibility tools and links are copied to the test site.
- This includes LTI 1.1 and 1.3 tools. LTI 1.3 links are downgraded to LTI 1.1 in the test site.
You can request multiple integration options, but some options may conflict.
Integration options:
- affect the entire ILP and all organizations
- can only be paired with a Refresh (cannot be requested independently)
- are included with any Refresh upon request
When you request a Refresh, include the integration options you want.
Delete All LTI
Option code: lti_delete-all
- Removes all existing LTI tools and links from the test site.
- Conflicts with
lti_1.1_and_1.3__clear_prod_keep_test
Maintain Existing Test LTI 1.1 and 1.3
Option Code: lti_1.1_and_1.3__clear_prod_keep_test
- Do not copy the Production LTI 1.1 and 1.3 Tools, Providers and Links to Test
- Keep the existing Test LTI 1.1 and 1.3 Tools, Providers and Links
- Conflicts with
lti_delete_all
Maintain Existing Test Extensibility and Valence Tools
Option Code: extensibility_tools__clear_prod_keep_test
- Do not copy the Production, Extensibility, and Valence Tools and Providers to Test
- Keep the Test Extensibility and Valence Tools and Providers
Maintain Allowed Local User List, 2FA, extra SSO settings
Option Code : authentication_SSO__clear_prod_keep_test
- Maintain Test Site Allowed Local User list.
- Maintain Test Site Two Factor Authentication (2FA) tokens.
- Maintain Test Site SSO Buttons and Login Settings.
- Maintain Test Site SAML JIT Config and Role Mappings
- Maintain Test Site OpenID Connect Mappings
- Maintain Test Site SAML IDPS, Keys and Metadata
Limit files / Reduce storage
Option Code: limit_storage_by_date
- Limit files that are available or copied to the non-production instance as part of a refresh.
- Reduce storage footprint of test sites allowing clients to focus their data purge work on production.
- If you provided a date (for example, 2024-03-24), files last modified before that date are removed from the refreshed test instance database.
- This does not affect data, only storage.
- If a test site user views a Dropbox submission that has been removed, the Dropbox submission will still exist and all data about the submission will exist.
- If you try to open the attachment there will be an error because the file doesn’t exist on test. The data exists, but you the file cannot be opened.
Affected file types
Limit files / Reduce storage affects the following file types:
- Quiz feedback
- Discussion attachments
- Dropbox user submissions
- Dropbox group submissions
- Dropbox user feedback
- Dropbox group feedback
- Locker groups
- Content
|
Note: Branding and logos are not affected. |