Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Users are redirected to this screen after successful login.

This screen consists of multiple sections and user interactions.

If the user is mapped to multiple tenants then a dropdown appears. The user can select the desired tenant to proceed further.

Once the user selects the tenant, the features cards are displayed on the screen based on the roles mapped for the selected tenant.

Login For First Time

YES → WalkThrough/User Guidance Enabled

NO → Home Screen

If the user logs in for the first time a system walkthrough begins automatically.

Else, users can view walkthroughs any time by clicking on the help icon.

Logic Implemented for Walkthrough

Create a global key for each card.

Create placeholder cards, pointer and description widgets.

On click, the position of the card is determined and the placeholder card appears on the overlay exactly.

Files Path

Primary Files https://github.com/egovernments/punjab-mgramseva/blob/develop/frontend/mgramseva/lib/screeens/Home/HomeWalkThrough/HomeWalkThroughContainer.dart, https://github.com/egovernments/punjab-mgramseva/blob/develop/frontend/mgramseva/lib/screeens/Home/HomeWalkThrough/HomeWalkThroughList.dart

Next → Changes the active index of the global key and repeats the same process outlined in the implementation logic

skip, End → closes the overlay

Home Screen - consists of multiple feature cards

Cards are displayed based on Role Access

Files Path

Primary Files https://github.com/egovernments/punjab-mgramseva/blob/develop/frontend/mgramseva/lib/screeens/Home/Home.dart

The home screen also consists of notifications. The notifications are customized for each user ID and user role.

Logic Implemented for Notifications

  • Individual API calls are made with the user ID and with the user role that merges both and notifications are displayed accordingly.

  • Close icon is used to mark the message as read, by making an update notifications API call.

  • View All button is used to navigate to the All Notifications Screen, where all the notifications of the particular user are displayed in pagination format.

  • Initially, only 10 notifications are loaded . The pagination drop down and right arrow click enable users to view more connections.

  • No labels