On this page we collect migration issues that will still have to be looked at for a full migration to the Target Technology Stack .
Impact:
Mobile Apps will not work any more
GOTHOMSIS & Payment Layer in TZ
Discussion:
C#-part can be re-used, but depend on stored procedures
done - needs to be compiled for .net core per Windows and Linux (done in Docker)
Mobile App on REST
Need new mobile app
ePayment on REST
migrate APIs to python
Interoperability on REST
e.g. GOTHOMISs & afyacare
done - Added to Docker packaging
done - issue with env variables (ex. DB connection string)
done - sharing of files (ex. Insuree pictures)
Test REST API against PostgreSQL
Impact: depends, will have to be collected per country by implementation partners
push for customizations based on module configuration
a lot of custom functionality
wip (tender in preparation as part of a general openIMIS maintenance contract)
payment layer through REST API
done - capitation payment configuration in Product
done - batch run
done - capitation payment SP
done - batch run SP
Impact: depends
Discussion: need to list remaining stored procedures that will not be migrated
will need to be migrated to PostgreSQL?
testing - PostgesSQL uses low isolation level by default - might solve the problem
wip
Impact: none
doesn't work in legacy version, not used
Impact:
Custom Access to MS-SQL DB
affects JSON-B column access
hinders upgrade to Django 4
Discussion:
wip
only a problem as long as s.o. is using MS SQL
maybe there are new drivers