Purpose of This Guide
This guide provides step-by-step instructions for implementing the Employee Records Management (ERM) v2.1. It covers all configuration, installation, integration, and validation tasks required to bring the solution from initial setup to production readiness.
Scope and Assumptions
This guide covers the full implementation lifecycle of the ERM solution, including VisualVault database configuration, document library and folder structure creation, document type setup, security configuration, module configuration, and go-live procedures. The following assumptions apply:
The VisualVault v6 platform is already deployed and operational in the target environment.
A VisualVault System Administrator completes the database setup for use during implementation.
The implementer has intermediate-level experience with VisualVault administration.
MySQL is the underlying database platform.
Required hosting agreement and subscription for ERM v2.1 and any add-on (if applicable) have been procured by the customer.
Intended Audience
This guide is written for VisualVault System Administrators and Professional Services Implementers responsible for configuring and deploying the ERM solution. Readers are expected to be comfortable with VisualVault administration, database concepts, and enterprise software configuration. Readers do not need programming experience.
End-to-End Implementation Summary
Implementation begins with verifying all prerequisites are in place: hosting agreement and subscription, platform access, and infrastructure readiness. First, the implementer submits a Change Control Form (CCF) with a support ticket to request that a System Administrator creates a VisualVault database and fills in the Customer record (General tab). The implementer then configures the ERM Customer, with customer-specific parameters, followed by any required integrations with external systems such as an secure file transfer protocol (sFTP) or identity provider (IdP). The solution undergoes structured testing before go-live, at which point end users are granted access and notified. Post-implementation, the implementer transitions the solution to routine maintenance and monitoring.