Task #65
Updated by Srishti Ghosh 18 days ago
**User Story** As a user, I want a consistent verification interface across Canofy ULIP services so that I can perform different searches and review verification results through a familiar and predictable workflow. **Description** # Develop a reusable UI and verification workflow framework for the Canofy ULIP application. A common multi-step workflow was established for verification-based services, allowing users to move through the process of Search → Review → Verification → Results. The framework includes common UI patterns for search-type selection, input fields, progress indicators, review screens, loading/verification states, success and failure messages, result cards, tables, action buttons and navigation between workflow steps. Common styling and layout patterns were also established so that individual ULIP modules can follow the same visual and interaction structure while displaying service-specific information. components. **Configuration / Prerequisites** Frappe application and custom pages configured. Common Canofy ULIP CSS/styling available to the application. Common page and wizard structure established. Search, review, verification and results workflow implemented. Common progress/ribbon component available for multi-step workflows. Common error, loading and success states defined. Individual ULIP modules connected to the common application/API layer. Includes: **Acceptance Criteria** * * [ ] Guided Wizard ULIP verification modules follow a consistent user workflow. * * [ ] Progress Indicator Users can clearly identify their current stage through the progress indicator. * * [ ] Result Cards Search inputs and search-type selections are presented consistently across applicable modules. * * [ ] Validation Components Users can review submitted information before initiating verification. * * [ ] Notification Components Verification/loading states provide clear feedback while an API request is being processed. Successful responses are presented in a structured results layout appropriate to the service. API failures and invalid searches are presented through clear user-facing error states. Users can navigate backward through the workflow without losing the relevant search information where applicable. Common UI components and styling can be reused across multiple ULIP modules. The UI remains separated from the underlying ULIP API implementation. **Test Cases ** TC01 – Verification Workflow Navigation Open a verification module and progress through Search → Review → Verification → Results. Expected Result: Each stage loads correctly and the progress indicator reflects the current stage. TC02 – Search Input Handling Select different supported search types and enter a valid search value. Expected Result: The appropriate label, description and input behaviour are displayed for the selected search type. TC03 – Review Before Verification Submit a valid search and proceed to the review stage. Expected Result: The selected search type and search value are displayed correctly before verification is initiated. TC04 – Verification Loading State Start a verification request. Expected Result: The user receives clear feedback that verification is in progress and is not left with an apparently unresponsive page. TC05 – Successful Results Complete a verification using a valid mock ULIP response. Expected Result: The results page displays the returned information using the common result layout. TC06 – Error Handling Test a failed search and a simulated server-error response. Expected Result: A clear error state is displayed and the user can return to the relevant search stage. TC07 – UI Consistency Across Modules Open multiple implemented ULIP modules. Expected Result: * * [ ] Shared workflow elements, styling, navigation patterns and interaction behaviour remain consistent while module-specific data is displayed appropriately. Styling