[RWB] Release 12.0 to RWB prod

[mahalakshme]

AC:

1. Do the steps mentioned in the below cards(used for deployment on RWB staging) - Pre-deployment in both cards, then deployment and Post-deployment in both cards.

• RWB release 10.2.1 to staging #1693
  - Also need to do the steps in this section: Already Done on RWB staging but not on RWB Prod:
• Release 12.0 to RWB staging env #1694
• For the mobile app release to 'Open testing' alone. Once clients complete the UAT testing, then we can promote to prod.
• Make sure RWB server works well with integration server
• Do the changes(adding custom query, etc.,) for GDGS2025-26 UAT org

[mahalakshme]

Test cases:

• Registration and Approval
• Encounter and approval
• Rejection -> resolution -> Resending for approval -> Approve
• Filtering on approval screen
• Sync of approvals to different device
• Sync between 7.3 and 7.3 apk
• Sync between 7.3 and 11.0 apk
• Media Viewer
• Upgrade from 7.3.0 to 11.0 apk
• Canned analytics disable

[AchalaBelokar]

@himeshr

• Media Viewer is not responding gdgs25-26uat org.

Screen Recording 2025-02-18 at 2.11.21 PM.zip

• when work order reject I try to edit the work order name is showing the indiara nagar dam

az_recorder_20250218_141803.mp4.zip

• when I fill the encounter it is not given to approval or reject tab..

[himeshr]

• Media Viewer is not responding gdgs25-26uat org.

Screen Recording 2025-02-18 at 2.11.21 PM.zip

Issue

The root cause for this is that, the org name includes "-", which causes issue while invoking sql query.

Current SQL query

SELECT media.id as id,
       media.uuid as uuid,
       media.subject_first_name as subject_first_name,
       media.subject_last_name as subject_last_name,
       media.subject_middle_name as subject_middle_name,
       media.is_voided as is_voided,
       media.created_by_id as created_by_id,
       media.last_modified_by_id as last_modified_by_id,
       media.created_date_time as created_date_time,
       media.last_modified_date_time as last_modified_date_time,
       media.organisation_id as organisation_id,
       media.image_url as image_url,
       media.sync_parameter_key1 as sync_parameter_key1,
       media.sync_parameter_key2 as sync_parameter_key2,
       media.sync_parameter_value1 as sync_parameter_value1,
       media.sync_parameter_value2 as sync_parameter_value2,
       media.subject_type_name as subject_type_name,
       media.encounter_type_name as encounter_type_name,
       media.program_name as program_name,
       media.concept_name as concept_name,
       row_to_json(address.*) as address,
       media.entity_id as entity_id
FROM gdgs25-26uat.media media
         JOIN gdgs25-26uat.address address ON address.id = media.address_id
where media.image_url is not null
  and media.is_voided is false
ORDER BY media.created_date_time desc;

Required fix

Enclose schemaName value withing Double-Quotes. i.e. gdgs25-26uat => "gdgs25-26uat"

[himeshr]

Responses to below issues are in-line

• when work order reject I try to edit the work order name is showing the indiara nagar dam => This is not an product issue, implementation has written rule to overWrite workorder name with LowestAddressLevel value

• when I fill the encounter it is not given to approval or reject tab.. => This is working as designed, confirmed that Entities with Enable_Approval are getting shown in Pending Card, and those without it, aren't.

[mahalakshme]

We have deployed 12.0 and not 12.0.1 - just noting for my reference

[AchalaBelokar]

• Register the farmer > pending > Reject > edit > Pending > Aprroved
• fill the farmer interaction this form is not having the approval status.
• Register the work order > Pending > approved
• fill the encounter of work order checked there approval status.
• Register the excavating Machine > approved then we can use this to work order.
• checked all this data is reflected on web app.
• upgrade to 7.3 to 12.0
• created the user check the password is changing screen is showing or not.
• Media Viewer
• Canned analytics disable
• checked old longitude export.

[mahalakshme]

@himeshr we decided to support the special characters in schema name in media viewer in standup. So basically the discussion was like anything that postgres allows we can support it. Will create a separate card for this.