Admin Fixes, Performance Improvements & Next Steps

 

Major Issue Found

The biggest issue discovered during testing was:

  • Users could not create a medication when the inventory table was empty

This completely blocked basic functionality for new setups.

This has now been fixed, and medications can be created properly even when starting from an empty state.

Admin Improvements

A large portion of the work focused on cleaning up the employee management flow:

  • Added automatic UserProfile creation during registration
  • Implemented a displayName update endpoint using userId
  • Refactored the Admin workflow to support:
    • Creating users with a name + role
    • Updating the display name directly from the table
    • Proper role assignment with cleanup of old roles
  • Replaced the role input with a dropdown instead of a text box
  • Added logic to detect what actually changed:
    • Name only
    • Role only
    • Both
    • No changes
  • Updated notifications so they reflect the correct action

Bug Fixes

User testing helped uncover and fix several issues:

  • Fixed duplicate user errors during registration
  • Fixed incorrect role reassignment when saving
  • Fixed display names not persisting
  • Fixed Admin modal behavior after actions
  • Ensured updates only run when changes are actually made

Also updated the Employee model to include:

  • id
  • originalRole
  • originalName

Layout Refactor & Performance Improvements

To improve navigation and reduce unnecessary reloads:

  • Moved MainLayoutComponent to a route-level wrapper
  • Removed <app-main-layout> from individual pages
  • Replaced ng-content with router-outlet

Profile Caching (UX Improvement)

A major issue during testing was UI flickering and repeated profile loading when switching pages.

This was fixed by caching profile data in ProfileService:

  • Implemented BehaviorSubject-based caching
  • Cached both profile data and profile image
  • Removed duplicate API calls on navigation
  • Fixed side navigation image flicker

  • Next Steps

    With the main functionality stabilized, the next focus is improving user feedback and UI consistency:

    • Improve notifications for temporary employee password errors
      • Show clear reasons for failure (validation, mismatch, requirements)
    • Update the UI color scheme
      • Improve consistency and contrast
      • Align with accepted design standards
      • Make the app feel more polished overall

  • Outcome

    After these updates:

    • Core functionality is no longer blocked (medication creation fixed)
    • Admin workflows are more reliable and easier to use
    • Role and name updates behave correctly
    • Navigation is smoother with no unnecessary reloads
    • UI flickering has been eliminated

    Overall, the app feels much more stable and closer to a production-ready experience.

Comments

Post a Comment

Popular posts from this blog

PharmaStock: Backend Infrastructure & Database Connectivity

 This week marked the transition from planning and design into real backend development. After organizing the project structure and defining use cases in previous weeks, I focused on building the technical foundation that the rest of the application will depend on. The primary goal was completing SCRUM-16, which involved connecting the ASP.NET Core backend API to a MySQL database and verifying that the system could successfully generate and manage database tables. I began by configuring MySQL to run inside a Docker container. Using Docker ensures that every developer on the team works against the same database environment, which reduces setup inconsistencies and avoids the common “it works on my machine” problem. Once the container was running correctly, I verified that it could be started, stopped, and inspected reliably. Next, I integrated Entity Framework Core with the Pomelo MySQL provider and registered the DbContext within the application. This step allows the backend to m...
Read more

PharmaStock Backend Progress Complete all backend endpoints

Image
 I completed the full Medication API (GET, POST, PUT, PATCH, DELETE) and finished SCRUM-37, implementing the stock quantity adjustment endpoint. Inventory quantities can now be increased or decreased, negative values are prevented, and all changes persist correctly in the database. I also finalized the inventory creation flow with duplicate lot validation and verified everything through Swagger testing. On the frontend side, I started SCRUM-38 and began building the Angular inventory list component to connect the UI to the new backend functionality. Overall, this week solidified the backend foundation and began transitioning into full-stack development. Medication Post Workflow            Medication Post          Post Inventory for new medication               Inventory adjustments
Read more

PharmaStock: Sprint Planning Complete

This week was focused on finalizing project planning and getting everything ready for development. I completed the setup of the Jira board , finalized all sprints for the full length of the project, and added clear completion criteria for each sprint and task. This gives the team a clear roadmap from MVP through enhancement features. I also synced my local GitHub setup with the main project repository and verified that the branching structure is ready for feature development. With planning complete and source control aligned, the project is now fully prepared to move into active development next week.
Read more