Implementation Data Validation Guide
Objective:
This guide is intended to provide suggestions for validating your data and configurations during each phase of the implementation.
How to Validate:
Use reports from the Settings section to compare system data. Test roles and permissions using test accounts. Take screenshots of the application. It is recommended to attach these reports and screenshots to your validation documentation.
Phase 2: Document Category Validation
Objective: Validate the configuration and functionality of document categories based on your original template.
Validation Items:
- Document Category General settings
- Workflows
- Roles/Permissions
- PDF export Options
- Custom Fields (if applicable)
- High-risk document attributes (see below for recommended focus)
- Document display
Recommended Reports:
- Category General Settings
- Documents: Document Category General and PDF Export Option Settings Report
- Category Permissions
- Documents: Document Category Permission Settings Report
- Category Workflows
- Documents: Document Category Workflow Settings Report
- Category Custom Fields (if applicable)
- Documents: Document Category Custom Field Settings Report
High-Risk Document Validation:
Use the Documents – Full Table to review high-risk attributes. Recommended columns include:
- Category
- Key IDs
- Effective Date
- Document State
- Author
It is recommended to export the table and compare to your original template to ensure accuracy.
Document Display Validation:
Review document display settings, including:
- Headers
- PDF rendering
- Workflow behavior
Validation methods:
- Spot-check migrated documents across multiple categories*
- Run documents through major and minor revision workflows
- Verify display settings for headers, watermarks, etc.
*This is especially important for documents with different settings for: headers, watermarks etc.
Permissions Testing:
- Use dummy accounts assigned to different roles.
- Use each account to test access and functionality across modules.
- Confirm that permissions match role-based expectations.