Hello Everyone,
I will be working on the Gsoc project : Integrating CFL’s Messages Module into O3 for the OpenMRS community.
I will use this thread to share the project updates and for general communication purposes.
Primary mentor: @pwargulak ,
Backup mentor: @druchniewicz , @samuel34
Objective
Develop an O3 UI, aimed at system administrators, to facilitate configuration of Message Services - create new one, upload SQL queries, configure configuration options.
Resources
excited to share the community bonding blogs
Looking forward to seeing your work on this feature @lumuchris256! Sending Messages e.g. via SMS is a feature many implementations/governements/businesses are looking for from OpenMRS, and your work will be valuable to them!
Hi @lumuchris256 Do we have a working repository for this ?
yes referenced here
while in the design phase , made the following observations 
that need more urgent clarity and technical perspective and guidance
The Current CFL impementation has a customised back end which handles the apis and validations within , done all together for their frontend. while O3 uses web services format
Integrating SMS and Messages modules into O3 leaves me at two approaches(current bocker)
Develop O3 UI based on the current backend of Connect for Life , which will be double work to restructure to current standard to use web services
Develop O3 UI according to current openmrs standards but then its backend and api resource doesnt seem a scope for the gsoc project ,any way to have one provided for?
In the move to have the SMS and Messages modules integrated into the Ref App at a later time will require to have a backend upto Openmrs current backend Standards serving the two frontend modules/packages in the communications mono repo
I might be wrong but whats the better technical approach and how to implement it best ?
(project resources up in the first post)
cc @grace @ibacher @samuel34 @dkigen @hadijah315 @pwargulak @druchniewicz @dkayiwa @vasharma05 @jexsie @jayasanka @piumal1999
For O3, we have to reimplement the UI logic based on the O3 framework packaged within an ESM and the OWA will be deprecated or maybe maintained for legacy systems.
The backend module should:
@lumuchris256 The messages module is a valid OMRS module. It does have a REST, it might not follow all conventions but it should not prevent making an UI. The current OWA is just a React app after all.
If the REST API, which fully conforms to the OMRS conventions is really needed, then me and @druchniewicz can make that for you.
2024-07-11T21:00:00Z
Mid term Update :
in the wake of the so far already done work towards the module ,
also have a second look at the latest project wiki for refined objectives . or even through the project’s QR code
here is the week 7 blog post