Virtual Agent Conversation Language BehaviorVirtual Agent (VA) requester conversation language is set when the Virtual Agent Web Client does its initial handshake with the VA server. If 'sysparm_requester_session_language' is provided when initializing the VA web client, then the value supplied with that sysparm is what drives the language of the conversation for the requester. If that value is not passed in, then the conversation language for the requester is set to the user's language preference. Starting in the Utah release, the requester's conversation language will not be updated for in progress conversations if no sysparm_requester_session_language is provided. If a user begins a conversation in english (language preference is English) and changes the user's language preference (to some other language e.g. French, Spanish, etc), then following a refresh of the portal page and VA Web client the requester's conversation language will remain in English. The system property 'com.glide.cs.preserve_requester_language_on_refresh' is set to 'true' by default. A value of 'true' preserves the requester's conversation language and leads to the behavior described above. If the behavior prior to Utah is desired, the admin can modify this system property to 'false' which would lead to the requester's conversation language changing after refresh to the updated preference for the rest of the current conversation. Any previous messages will remain in the initial language that was set. It is recommended that the system property remains 'true' for any Virtual Agent deployments using the Language Detection feature.