Description
For both legacy webchat (/webchat) and aselo webchat clients (/aselo-webchat-react-app), data ffrom the pre-engagement form is supposed to be transferred to the new contact form in flex provided by the /plugin-hrm-form plugin.
This data is read and transferred from the Twilio task to the HRM contact when it is created in the twilio lambda (/lambdas/account-scoped)
This is not happening specifically in the case of Multi Select fields, i.e. fields where several options are selected. Typically, single select fields in the pre-engagement form are mapped to the multi select field in flex, and a single option is expected to be preselected based on the service users selection, but none are
This issue is being seen in both clients so is likely either an issue with the Twilio Lambda transferring the data to the contact or the flex plugin displaying the prepopulated values
Steps To Reproduce
- Run a local copy of Flex pointing at CA_STG
- Set the worker to available
- Open the legacy Webchat for CA_STG Client at https://assets-staging.tl.techmatters.org/webchat/ca/test-chat.html
- Complete the pre-engagement phase including the gender dropdown
- Complete the chatbot
- Accept the new task in Flex and wait for the contact to be created
Expected behavior
Gender checkbox set on the flex contact form has the selection made in webchat checked
Actual behavior
All Gender checkboxes are empty
Additional context
This issue was probably introduced between v2.51.0 and v2.52.0
The implementation for the HRM service that creates the contact is open source, here: https://github.com/techmatters/hrm
Description
For both legacy webchat (/webchat) and aselo webchat clients (/aselo-webchat-react-app), data ffrom the pre-engagement form is supposed to be transferred to the new contact form in flex provided by the /plugin-hrm-form plugin.
This data is read and transferred from the Twilio task to the HRM contact when it is created in the twilio lambda (/lambdas/account-scoped)
This is not happening specifically in the case of Multi Select fields, i.e. fields where several options are selected. Typically, single select fields in the pre-engagement form are mapped to the multi select field in flex, and a single option is expected to be preselected based on the service users selection, but none are
This issue is being seen in both clients so is likely either an issue with the Twilio Lambda transferring the data to the contact or the flex plugin displaying the prepopulated values
Steps To Reproduce
Expected behavior
Gender checkbox set on the flex contact form has the selection made in webchat checked
Actual behavior
All Gender checkboxes are empty
Additional context
This issue was probably introduced between v2.51.0 and v2.52.0
The implementation for the HRM service that creates the contact is open source, here: https://github.com/techmatters/hrm