2024-01-25 openIMIS/CORE-MIS Developers Workshop - Day 3, Thursday

Content

Schedule

Main event: https://openimis.atlassian.net/wiki/spaces/OP/pages/3670638593

Start

End

Program

Who

Tools

09:00

10:00

  • Sao Tome test data import / data upload adjustments

  • payments

@Damian Borowiecki @malike

 

10:00

11:00

Weekly Developers' Call

@Uwe Wahser

 

11:00

11:15

Coffee break

 

 

11:15

12:30

  • payments

@Damian Borowiecki @malike

 

12:30

13:30

Lunch

 

 

13:30

15:30

  • payments

@Damian Borowiecki @malike

 

15:00

15:15

Coffee break

 

 

15:15

16:15

  • test cases & test link

@Patrick Delcroix

 

16:15

18:00

Evaluation Hackathon:

  • Sao Tome test data import (success)

  • open search (success)

@Seweryn Niedzielski @Kamil Malinowski

 

Relevant Resources

Minutes

I. DISCUSSIONS - excel requirements file and test link

  1. Payment points

    1. Payment point manager is not mandatory for creating the payment point

  2. Payroll and Payment Mode

a) The 'Payment Point Manager' field should be optional at the database level in the 'Payroll' table. Specifically, for Offline mode (CSV reconciliation) and Online modes (strategies), the 'PPM' dropdown should be disabled for adding a payment point manager, as it is redundant for those strategies. However, for the Mobile Payment strategy, this option is mandatory. (PPM is a main user of PPM mobile app)

  1. Payment plan

    1. We need to change the way of how rebates are added on the benefit plan level. Currently, user is able to choose the rebates with using the advanced criteria on payment plan level - this is confusing. We need to move it below, under the general view on payment plan creation modal

  2. Testlink

    1. for every test suite we need to repeat parent

    2. if a test suite is empty the system will use the one above for a particular test case

    3. it’s important to indicate a test steps and expected outcome on a test case level so the tester can fail certain step, no whole test case

    4. once test cases (with a proper test steps) are filled we need to put it directly into the testlink server

    5. file is uploaded into the testlink server by maintenance team; the responsible of the others is to fill the excel file with test cases

  3. Test process clarification

    1. Test cases need to be transfered to the test link after every sprint (once certain functionality is created and delivered for UAT)

    2. World Bank Team will conduct the test on the testlink platform

 

II. HACKATON

OpenSearch hackaton:

  • open search - things to do

    • possibility to add new dashboard (ideally also removing) from UI web (remember about permissions)

    • block edit from dashboard in embedded mode from openIMIS

    • admin can edit, other users cannot edit dashboards (managing dashboard view)

Hackaton - Upload Individual - hackaton branches (upload prototype - NOTE: it is still under development and it’s not production ready!). Necessary changes to have a demo of this prototype on local environment:

  • small adjustment in workflow module - this commit

  • need to add spinner to load, need to work on performance in opensearch synch and later have a workflow in lighning (currently it is a python one)

  • need to think about json_ext fields that could be not written in english

Open topics / questions

Did you encounter a problem or do you have a suggestion?

Please contact our Service Desk



This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. https://creativecommons.org/licenses/by-sa/4.0/