Replai Knowledge Layer
Understanding your legacy application through recovered metadata and business intent analysis
2 Modules•5 Forms
6 Cross-module
Low complexity
12 this week
Well-Structured Module Architecture
Your application follows a clean modular design with clear separation between SampleApp and ReportModule. This semantic structure will simplify modernization to microservices or cloud-native architectures.
Cross-Module Dependencies Detected
EmployeeReport references DataBlock across module boundaries. Our semantic layer reveals the business intent - consider creating a service boundary to enable independent deployment during modernization.
Business Logic Metadata Recovered
EmployeeLOV used by multiple forms - our semantic analysis reveals this represents a reusable "Employee Selection" business capability. Can be rebuilt as a shared component in any target stack: React, Angular, or Oracle Apex.
Analyzed MainForm dependencies
Sarah Chen • SampleApp Module
Asked about trigger optimization
Michael Rodriguez • WhenNewFormInstance
Exported dependency report
Sarah Chen • Full Application
Identified circular dependency
Alex Thompson • ReportModule