When adding context.portal condition on Advanced work Assignment service channel chats does not workIssue Sometimes, users may be interested in setting conditions that determine which queue an interaction will be directed to based on the portal it is created from. In these situations, users may try to add conditions "Context. portal = x" (where "x" is the name of a portal) onto service channel records. However, This is found to not work as expected. Steps To Reproduce: Navigate to an active awa_service_channel that is associated with a working awa_queue record on the instanceIn the conditions for for the awa_service_channel "Chat" channel, add the condition "Context.portal contains X" OR "Context.portal contains X" (X being the url code for a portal where AC can be triggeredEnsure that an agent from the active awa_queue is active on a working workspace and set to the "Available" stateAs a separate user, navigate to portal X (either SP or ESC or CSM)Attempt as an end user, open the virtual agent chatbot and make sure that the "Live Agent" option can be selected.Select "Connect with Live agent" Expected behaviour: As the end-user is triggering an engagement from Portal X, it is expected that this will meet the conditions set within the awa_service_channel (Context.portal = X Actual behaviour: Engagement does not take place, and not even an awa_work_item record is shown to be created.ReleaseUtah CauseThis is considered expected behavior. Service Channels conditions are used to query interactions that needed to be routed, and dot-walked remote table conditions like "context.<x>" are not queryable, so cannot be used for this purpose. ResolutionAs a means of working around this behaviour, the context.portal conditions can still be applied to awa_queue records instead.