Introduction
Welcome to Bumis.app, your comprehensive solution for managing repair and construction requests in educational institutions. We are excited to announce the launch of Bumis 3.0, a significant upgrade from our previous version.
Why these changes?
The transition to Bumis 3.0 is driven by our commitment to provide a faster, more efficient, and flexible platform. By using the powerful Drupal platform, Bumis 3.0 offers enhanced performance and the ability to expand and adapt the system incrementally.
About Bumis 3.0
Bumis 3.0 is a complete rewrite of the Bumis 2.0 application, built on the Drupal platform. This upgrade enables us to introduce new features and transform functionalities to better meet your needs.
Data Migration
To ensure continuity, we have carefully migrated all existing data from Bumis 2.0 to the new Bumis 3.0 site, which can now be accessed at the new domain: bumis.app.
Security and Passwords
For security reasons, users’ passwords have not been migrated. All users will need to recover their access. Detailed instructions for password recovery can be found below.
Ongoing Testing
Please note that the system is currently in the acceptance testing phase, and there may be some issues. If you encounter any problems or have difficulties, please contact us at [email protected].
This revision clarifies the transition and benefits of Bumis 3.0, outlines the data migration process, and provides information on how users can regain access to the system.
How to login to the new system
In order to authorize in the new system, you should do the next steps:
- Go to https://bumis.app/ - you will see the login screen.
- Press “I forgot my password” in the left corner - you will see the “Reset password” popup.
- Enter your email address and press “Submit”.
- Check your email and find the mail from the system with a one-time recovery link.
- Press the link and setup your password.
- Save the changes.
- Now you can log in to the system with your email and new password.
Migration of the data
Important! There are 6 incidents missing now in the migrated data. We detected the problems with these incidents during the migration, and now we are fixing these problems.
As soon as we fix the problem, we'll restart the migration and the missing incidents will appear in the next migration data.