Validating in Test Environments

To validate disposition functionality within a test environment (UAT or preview):

1. Validate Disposition Workflow: Create retention policies in the test environment (UAT or preview) using the retention policy creation UI. Smarsh also follows a similar process on test or sanity environments during the product development lifecycle.

2. Prepare Test Data: Prepare a test data set to be ingested into the test environment for validating retention policy expiry and document holds.

3. Data Ingestion:

   • For Tier 1: Ingest the test data set into the archive using the Data Ingestion API. Utilize ingestion logs for troubleshooting.

   • For Tier 2: Create a new Salesforce case and attach the test data set. Smarsh will process these messages internally and notify upon completion. Record transcript ID values for later search reference.

4. Policy Assignment:

   • For Tier 1: Policy assignment is automatically triggered upon data ingestion.

   • For Tier 2: Contact your Smarsh customer representative to initiate policy assignment within the test environment.

5. Disposition Activation and Reporting: Once policy assignment is complete, request Smarsh to activate disposition in the test environment. Verify that the Proof of Deletion or Disposition Summary report is enabled for the designated test users.

6. Test Scenario Validation: Validate various test scenarios by modifying policy definitions, creating document holds, or updating Conduct queues. You may refer to the list of test scenarios used internally by Smarsh for creating your own test cases.
   

   Policy Behaviour	Holds Behaviour	Disposition Expected
   Any one of the applied policy has expired, however other policies are still in effect.	No impact	No
   All policies expired	No holds applied, or all existing holds are released	Yes
   All policies expired	One or more holds applied	No
   Reduce retention period on operational policy, and it expires. But other policies are still in effect	No impact	No
   Reduce retention period on operational policy, and it expires. No other policies are in effect	No holds applied	Yes
   Reduce retention period on operational policy, and it expires. No other policies are in effect	One or more holds applied	No
   Increase retention period on an expired policy. No other policy is in effect.	All holds are released	Yes Note Tier 1 allows users to extend the deletion process for documents that have reached their expiry date, but within a grace period of 3 days
   Increase retention period on an active policy. No other policy is in effect.	All holds are released	No

   Note

   Legal hold policy behavior and scenarios are similar for conduct queues.

7. Document Search and Retention Verification: Use the previously noted message or transcript IDs to search for the documents within the archive search functionality. Leverage the retention tile functionality within the search interface to verify which retention policies or holds are currently applied and active for each document.