...

• Uwe Wahser

• Dragos Dobre

Topic Proposals:

• GovStackSandbox: Q&ABest practices for openIMIS customization

Presentations / Attachments

Minutes

• Step one (Gofer):

• install full openIMIS version in a cloud environment → image without REST APi is being provided

Step two:experiences from Cameron implementation project. Some developments were done as modification of the existing models, so need to detail how these can be done properly

• What compliance testing means?

• What score (% of tests passed) makes a BB compliant to GovStack?

• Which BB is tested during a compliance testing?

• Who makes the requests and who execute the business during the compliance testing?

• Is there a standardized integration protocol (i.e. for payment systems) or each system has its own integration protocol (has different test cases/gherkin per protocol or there is a mediator that makes some standard ETL to custom)?

• How the testing is managed (one-by-one or globally with one run)?

• What’s the periodicity/limit of compliance testing (every new version of BB or once per period/year)?

  • Inspiration

    • https://

    govstack-global.atlassian.net/wiki/spaces/DEMO/overview

    • github.com/openimis/openimis-be-claim_ai_quality_py

    • https://

    govstack-global.atlassian.net/wiki/spaces/DEMO/pages/161251348/Integration+themes

• Step three: Business Overview

  • Frontend walk-through

Questions

(carried over from last week)

• • • github.com/openimis/openimis-fe-claim_ai_quality_js

  • Frontend (React)

    • the various forms expose contribution points that additional modules can inject their own components

    • some forms might not have the contribution part already available, it is great to add them or fix them (Blsq just did fix a ClaimForm contribution point)

    • idea: build a form mask to know if the fields are displayed or not

      • to be used in future workflow functionality

  • Backend

    • use managed tables

    • extend by using json_ext, table fields or dedicated table

    • how can we extend GraphQL objects ? Adding new mutations and queries is fine, just define them in schema.py in your own module and it’ll be included. Overriding GQLType objects to add fields might

  • Dragos and Damian to train developers in Tanzania next week

    • inspiration for future video tutorials

  • We should probably dedicate a Wiki section for developer onboarding, examples and troubleshooting

Questions

Additional Resources