Master Lex Web UI CloudFormation template update from (v.0.21.5) to (v.021.6)

[ijmoya]

We updated our cloudformation stack from v.0.21.5 to v.021.6 and we started getting reports that when our agents accept the chat they are not able to see the users responses. They just see (###).

For EX: Bot Transcript: (1\1) 10:17:00 AM Bot: Hi, I'm Mari. I'm here to help with all of your financial aid questions (y en español) or click the 'Help' icon to get started! 10:17:06 AM Human: ### 10:17:13 AM Bot: ### 10:17:33 AM Human: ### 10:17:33 AM Bot: ### 10:17:53 AM Human: ### 10:18:00 AM Bot: ### 10:18:11 AM Human: ###

I have attached a CTR (0e2239ec-c753-4a2f-b720-8836c85d21f0) but it looks like all contact trace records from Jan 17th to present are showing the same thing.
Stack ID(s) / Stack ARN: arn:aws:cloudformation:us-west-2:999656178089:stack/lex-web-ui/cdd517e0-613c-11ed-9d7c-02d7659e0879

0e2239ec-c753-4a2f-b720-8836c85d21f0.json

[atjohns]

Hi, I was just able to replicate this on v.021.6 as well. It looks like potentially one of the packages that did the RegEx check on whether responses get redacted is misbehaving. Looking into a fix now.

[ijmoya]

Thank you for the quick reply! Looking forward to your response.

[atjohns]

Ok yes, there is some issue regarding how RegEx is handled now that I will fix in a patch later this week. For now, if you want to fix this you can change your lex-web-ui-loader-config.json file manually and get it working properly.

You should see a line called transcriptRedactRegex in the connect section of the config file. It is probably blank as that's the default and what is causing the problem, however if you provide a RegEx that will match to nothing it will work (as nothing will match and nothing will get redacted).

So, basically, change it to this:
"transcriptRedactRegex": "a^"

and you should be good to go for now.

[ijmoya]

Okay, I will give that a try and keep you posted. Thanks once again. Let me know when you have implemented your fix. Thank you!

[ijmoya]

I implemented your suggested fix and it worked. Thank you kind sir!

[atjohns]

Closing as release v.0.21.7 should resolve the issue moving forward.