Hidenori Saito

Usually, our operator in dealer is using this whenever need to contact particular opportunity, order or such using customer description, vehicle registration number or such, and if exact description or number is needed for search, they need to check and recognize those form 100% in any database or document in advance to search it.

For example. for search with customer description, they need to clearly input correct byte, correct space and correct special characters such as registered in DB in case of search with Equal. Especially for the byte, it is quite critical in Japanese language that several single byte and double byte are mixed up in the description as Customers applied.

Under the situation, Equal is not used at all in search, but Contains is used as most frequent in our dealer.

Since single byte and double byte are existing in Japanese language, it is difficult let user to set single byte of special character as mandatory in just search in our operation.

Also in user operation, our user are unable to convinced why need to input the character which is not included in work they want to search.

Under the situation, would like to request to remove inputting " * " from general search, but only with word user wants to search.