Browser AutoComplete in New Ticket

[mcampbell]

I am trying to figure out how to enable the individual browsers to autocomplete the To customer field. I couldn't find anything that looked relevant in a search of this forum. And I tried something I saw elsewhere on the web, but that generated undesirable errors when trying to submit tickets.

Any ideas?

Thanks.

[jojo]

Autocompletion of the To in the Agent Interface is not browser relatet as it is done by AJAX from the customer database

[mcampbell]

I'm aware that by default the autocomplete feature in OTRS accesses its own internal database via the AJAX code. But for a variety of reasons, I am not using this feature at this time. My question is about how to enable the browsers to have autocomplete (since they are currently disabled from allowing it). As per the link I posted in my OP, it used to be possible in older versions to dig around in the code and enable this, but apparently not in 3.1.x

[crythias]

I'm aware that by default the autocomplete feature in OTRS accesses its own internal database via the AJAX code. But for a variety of reasons, I am not using this feature at this time.

The autocomplete is almost always a javascript ajax component that queries *something* from a server (or sometimes a js array)

My question is about how to enable the browsers to have autocomplete (since they are currently disabled from allowing it)

Look at the dtl that references the screen they're not allowed to autocomplete from.
Look at the code surrounding the field they're going to auto complete.
change the code to be autocomplete from your data source OR
just remove the ajax component and let the browser try to remember.

[mcampbell]

Look at the dtl that references the screen they're not allowed to autocomplete from.
Look at the code surrounding the field they're going to auto complete.
change the code to be autocomplete from your data source OR
just remove the ajax component and let the browser try to remember.

Could you be a little more specific? I'm only really understanding what you're saying on the highest of levels, which kinda mirrors what I see in the link I posted up top for the older version of OTRS. The newer one is apparently different, because trying to follow the directions reveals "missing" files, so I can't complete what it says to do. Because it's different, I don't really know what I'm looking for now, because I haven't seen anyone post anything for newer versions of OTRS.

[crythias]

My question is about how to enable the browsers to have autocomplete (since they are currently disabled from allowing it).

Look at the dtl that references the screen they're not allowed to autocomplete from.

What screen are we talking about? It has a name/Action in the URL. That URL has a related .dtl file in Kernel/Output/HTML/Standard/[action].dtl

Look at the code surrounding the field they're going to auto complete.

Edit the file from above and search for the field that you want the browsers to autocomplete. It has javascript surrounding it.

change the code to be autocomplete from your data source OR

change the code to reflect what you want to happen. By default, you do nothing, and let it autocomplete from the customer back end like OTRS is already programmed to do.

I'm aware that by default the autocomplete feature in OTRS accesses its own internal database via the AJAX code. But for a variety of reasons, I am not using this feature at this time.

just remove the ajax component and let the browser try to remember.

delete all ajax code surrounding the field. Just make it an input type=text. If you don't understand this part, stop. It's probably not going to be how you want it.

because I haven't seen anyone post anything for newer versions of OTRS.

your sig says version 3.1 Most things you'll find on this forum are related to 3.0-3.2. 3.3 is newer version and doesn't apply to you. Unless it does and then you'd say, "I'm using version x" and "I saw this link (which?) and it relates to version y."

I don't really know what I'm looking for now

Me neither.