Handover

I. Inventory and Documentation

1. Summary of tools/technologies used:

a) database

• postgres

b) backend

• Python, Django, graphQL

c) frontend

• React JS

d) dockerized distribution and external components:

• https://github.com/openimis/openimis-dist_dkr/tree/coremisSetup

• openFN lightning (https://github.com/openimis/openimis-lightning_dkr )

• OpenSearch

• OpenSearch Dashboards

2. Summary of the documentation:

a) Backend

• for assembly https://github.com/openimis/openimis-be_py/tree/coreMIS

• for coreMIS modules see backend modules (be)

b) Frontend

• for assembly

• for coreMIS modules see frontend modules (fe)

c) Database

• - postgres container (db)

d) dockerized distribution and external components

• - setup openIMIS dockerized distribution

• - openFn Lightning setup

• - openSearch/OpenSearch Dashboard setup

e) Documentation on Confluence page:

• README.md sections of all modules presented in coreMIS package

• - tasks management module maker-checker logic

• - payment modules design

• module mapping

f) User guides :

II. Access Details

1. Transfer critical system/application logins.

a) coreMIS demo server - no production data

• URL

• Login: Admin

• Password: admin123

b) coreMIS demo lightning credential - no production data

• URL https://coremis-etl.s1.openimis.org/users/log_in

• Login: IMISUser@openimis.com

• Password:  IMISUserPassword

c) OpenSearch Dashboard demo server

• coremis.s1.openimis.org/opensearch/

• NOTE: You have to log into openIMIS to access OpenSearch due to the nginx configuration.

2. Update access list post-handover.

3. Ensure secure credential transfer.

• there is no credentials to production instance because currently we do not have any production data

IV. Ongoing tasks and responbilities

List of the created but not addressed task is also available under this link

1. Document in-progress tasks.

2. Document recurrent or routine tasks

   • No reccurent or routine tasks were spotted during the development.

3. Identify unfinished tasks for the next tender.

   • Unfinished tasks are described above. However, there are several major things that surely need to be included in the next tender:

     • Integration with Mobile App

     • On-site payment

     • Goods Disbursement

     • Grievance Module

     • OpenSearch roles

     • Payroll Creation for Ad-hoc payment with CSV Upload

     • Payrolls for Payment Point Manager Reconciliation

     • Manual CSV/Excel File reconciliation

     • Payment History

III. Environment Details

1. Environments:

a) coreMIS demo server - no production data

• URL

• Login: Admin

• Password: Admin123

b) coreMIS demo lightning credential - no production data

• URL https://coremis-etl.s1.openimis.org/users/log_in

• Login: IMISUser@openimis.com

• Password:  IMISUserPassword

c) OpenSearch Dashboard demo server

• coremis.s1.openimis.org/opensearch/

• NOTE: you have to log into openIMIS to access openSearch

2. Differences

• The backend assembly is built based on coreMIS branch

• The frontend assembly is built based on coreMIS branch

• dockerized distribution for coreMIS is available here on coremisSetup branch

• Additional coreMIS modules: openimis-fe-payment_cycle, openimis-be-payment-cycle, openimis-be-payroll_py, openimis-fe-payroll_js

Open

regarding data structure - here you can find more details how it is managed now and how it could look in next project phases

• The frontend has additional configurations that change the position of the menu and redirect links when clicking the help icon. Here you can find more details how to change it (menuLeft, redirectToCoreMISConfluenceUrl).

• coreMIS frontend nginx.conf (openimis.conf) - here, there are additional directives for OpenSearch Dashboards and openFN lightning. https://github.com/openimis/openimis-fe_js/blob/coreMIS/conf/openimis.conf

3. Deployments

• In every module, there is a GitHub workflow (example: https://github.com/openimis/openimis-be-social_protection_py/blob/develop/.github/workflows/core-mis-test-server-deploy.yml) to execute deployment to the test server once a PR is merged into the develop branch.

• You can manually rebuild it on the GitHub Actions page, as shown in the screenshot below (see bold 'CoreMIS Server Deployment job' option):

Open

4. Access to server and release process

• The server is maintained by the SwissTPH team.

• The openIMIS has biannual releases, occurring in April and October each year

• The release process involves creating branches related to the release (release/<month-year>). Once all the necessary preparations are complete, this branch is merged into the main branch, and the packages for Python and React are created with the appropriate version tags.

• The team responsible for maintaining the project is in charge of handling the releases.