UI Policy not working with dot-walked conditions

[mcarpenter]

I am trying to create a UI Policy for the Incident that looks a field on the sys_user table to trigger. It looks like this:

When to apply:

Caller.agent (caller_id.u_agent) is 'True'

UI Policy Action:

Agent chat(u_agent_chat) is Visible

This is not working as expected.   The Agent chat file is only available after the Incident is submitted.   I think that it must be due to the fact that the conditions is dot walking to another table.   If this is the case, what is my next best option? Client script?   If client script, what would that script look like?

Any help is appreciated.   thanks

[karthik73]

Hi Michael,

I do not think dot walking is the issue, are there other UI policies/ client scripts that could be conflicting with this UI policy?

[mcarpenter]

I don't think so the "Agent chat" field is a field that I just created right now.

[Goran WitchDoc]

Remember the UI Policy hits on client side, which means that if you dot-walk this field needs to be on the form.. it can be hidden, but it must be on the form.. I would say it's buggy, but this is how it was the last time I had to do with this.

if you don't want it on the field, you should be able to like put in the g_scratchpad with a display Business rule, then look at the value there to decide what to do.

//Göran

[PTR]

Hi All,

What is 'type' of Agent(u_agent)  field in the Incident form and in  UI policy condition i am uable to see the 'Agent' field for dot walk like  Caller.agent even i can see remaining OOB fields of Incident record

Thanks,.