Webhook & schema changes to monitor custom contact info

[Satendra-SR]

Is your feature request related to a problem? Please describe.
Initially, there was not much custom contact info that we were planing to capture, but as of now, we are capturing different custom contact information for a contact.
We need to capture these information in our database for generating relative matrices.

Describe the solution you'd like

• List down the contact info we would like to capture.
• Check whether we are getting these information from RP (We are getting contact group info, these should be available as well).
• Come up with the new schema design based on the
• Make code changes to implement the feature request.

Describe alternatives you've considered
None

Additional context
None

[Satendra-SR]

@prtkdost Assigning it to you for first round. Can you take the first point. We will need a list of what all custom dataset we are capturing and that needs to be captured in out database as well.

[Satendra-SR]

List down the contact info we would like to capture.

• These are the dynamic contact fields and can be added more in future.
• We need to come up with a plan so that we can incorporate new fields as well.

[Satendra-SR]

Check whether we are getting these information from RP

We can get these contact fields details using contact.groups variables we have in RP.

---

RP flow post payload

---

Json object

[Satendra-SR]

Sharing the proposed schema for capturing custom contact details

Table name: user_contact

column	type	foreign key
id	int
user_id	int	user -> id
registration_id	int	registration -> id
user_phone	varchar
flow_run_uuid	varchar
field_name	varchar
field_value	varchar
created_on	timestamp
updated_on	timestamp

[Satendra-SR]

Capture only fields with prefix dost_

[Satendra-SR]

This is deployed on UAT and ready for testing.

Note: Please use these two flows for testing or create new for testing.

1. DOST-Test-P2M7D4-devteam
2. FINAL-DOST-test-OnboardingCall-devteam

Steps to test:

1. Schedule a call from above flows.
2. Check user_custom_fields table for latest entry for your phone number.
3. Check the table is populated with correct user contact information.

[Satendra-SR]

This is deployed and working fine on production as well.

[Satendra-SR]

Need to check dost_flow_status

[Satendra-SR]

Working as expected on prod. Closing.