Glific message sending to user not working

[mahalakshme]

Issue:

On trying to save a user, inspite of the right Glific config, user doesn't receive the message.

Details

User : sachink@gdgsgom
org : gdgsgom
env: Gramin server => https://app.rwb.avniproject.org/#/

Analysis:

In rules-server logs has the below:

 Headers from req: sachink@gdgsgom undefined 26b69dfd-0994-4821-8244-471684d13e8f
1|rules-se | Error: Value of entityType param is invalid
1|rules-se |     at _callee4$ (/opt/rules-server/src/RuleExecutor.js:89:15)
1|rules-se |     at tryCatch (/opt/rules-server/node_modules/@babel/polyfill/node_modules/regenerator-runtime/runtime.js:45:40)
1|rules-se |     at Generator.invoke [as _invoke] (/opt/rules-server/node_modules/@babel/polyfill/node_modules/regenerator-runtime/runtime.js:274:22)
1|rules-se |     at Generator.prototype.(anonymous function) [as next] (/opt/rules-server/node_modules/@babel/polyfill/node_modules/regenerator-runtime/runtime.js:97:21)
1|rules-se |     at asyncGeneratorStep (/opt/rules-server/src/RuleExecutor.js:22:103)
1|rules-se |     at _next (/opt/rules-server/src/RuleExecutor.js:24:194)
1|rules-se |     at /opt/rules-server/src/RuleExecutor.js:24:364
1|rules-se |     at new Promise (<anonymous>)
1|rules-se |     at /opt/rules-server/src/RuleExecutor.js:24:97
1|rules-se |     at executeMessagingRule (/opt/rules-server/src/RuleExecutor.js:85:34)

So looks like the rules-server in RWB env is not updated. In RWB env, 6.1 versions are installed. But the commit that has the right entityType in rules-server is in 7.0 branch of rules-server.

Acceptance criteria:

• Deploy the appropriate version of rules-server to RWB env
• Tag the commit appropriately and update in the 'Branch details' column in the release tracker
• Make sure Gliffic message sending to users work in RWB env

[himeshr]

@AchalaBelokar refer to https://avni.readme.io/docs/writing-rules#13-message-rule and https://avni.readme.io/docs/whatsapp-integration#how-it-works for info on the related features.

[AchalaBelokar]

• Tried with this org it is not working

[mahalakshme]

@AchalaBelokar moving this to Done, since implementation team verified this