Hi Kubig,
I thought this might help as well, here’s what it shows in the logs:
05:19:18.387 Trc 21126 [SvcSrvW-10] <844> ‘OMInteractions.GetInteractions’ (request id 844) handling duration : 9 ms.
05:19:21.356 Trc 21124 [ESP:4400] Request (queued for 0 ms): Id=2|Type=Request|AppName=UCS_Provider|AppType=|Service=Index|Method=Search.
05:19:21.356 Dbg 21291 [SvcSrvW-6] Thread ‘SvcSrvW-6’ registers to shutdown notification.
05:19:21.358 Trc 21124 [SvcSrvW-6] <2> Request (queued for 1 ms):
Id=2
Type=Request
AppName=UCS_Provider
AppType=
Service=Index
Method=Search
Parameters=
[
IndexName=“interaction”
MaxResults=100
Query=“StrAttribute9:”[email removed]“”
tkv.multibytes=“false”
]
UserData=
[
].
05:19:21.361 Trc 21000 [SvcSrvW-6] <2 tcp://192.168.60.1:51233> Service ‘Index’ method ‘Search’ started.
05:19:21.393 Trc 21001 [SvcSrvW-6] <2> Service ‘Index’ method ‘Search’ ended, processing time (ms): 32.
05:19:21.394 Trc 21125 [SvcSrvW-6] <2> Response:
Id=2
Type=Response
AppName=ContactServer
AppType=CONTACT_SERVER
Service=Index
Method=Search
Parameters=
[
Documents=
[
]
FoundDocuments=0
ReturnedDocuments=0
]
UserData=
[
].
05:19:21.395 Trc 21126 [SvcSrvW-6] <2> ‘Index.Search’ (request id 2) handling duration : 40 ms.
Hi Kubig/Cavagnaro,
Did you find out anything about this?
Appreciate any help. Still struggling with this.
I will try to make a test in my lab env today and let you know with a result
Thanks Kubig,
Appreciate your help.
Did you follow this link http://docs.genesys.com/Documentation/ES/8.1.4/Admin/UCSSearchMake ? I am not at my PC yet, so still without my tests 
Hi Kubig yes we did follow the instructions in that manual and if you look at some of the replies that I have mentioned above you will see that the fields from Interaction entity are mapped to the searchable columns and when I query the interaction table I do see the string attribute columns getting populated with the values as well so I hope and believe that I have configured, so I hope and believe that I have configured it as per that document unless this document in itself is missing something. And this brings me to think if there’s something while installing the UCS App or DB server if we have to do something to enable this search functionality, which I i am pretty sure is configured already as otherwise i will not see the index attributes created and being enabled at the ucs level.
Using IWS does it works?
Hi Cavagnaro iWS only supports looking for contacts primarily and then for that contact it brings History from Interaction table. Correct me if I am wrong. So in essence I can look for contacts from the contact entity using iWS.
You are not right, IWS allows to search by any available interaction data within UCS database.
Hi Kubig,
Please correct my understanding, when I go into iWS and click the Contact button in the iWS toolbar, I get 2 panels one for the Contact Search and another for the Interaction History, now if I provide anything directly into the Interaction History panel, nothing comes up but when I search for a particular contact and then it brings along the history for that contact and then I can search within those Interactions for that contact.
Secondly: I have let’s StrAttribute9 mapped to PFS_id, and under the options for the iWS application in the GA I provide the PFS_id to be a column to be listed in the Interaction History panel and then search for the records that have content for the PFS_id, it brings up those records, but when I do it for mapped column which is StrAttribute9 it doesn’t bring up anything.
Hope it helps.
Let me know if you need anything else in this regard,
By the way were you able to test it out in your environment.
Hi Kubig,
Were you able to run this in your environment?
Let me know please.
Hi Kubig/Cavagnaro,
Any help is much appreciated in this regard.
Hi, sorry for delay. I did made a quick test and you are right and it does not work as expected. Unfortunately, I have not got time for deep investigation (read directly the Lucene and look at the available “columns”) - so, try to test it yourself and let us know, what is the result.
Hi Kubig,
Thanks for the response, can you tell me at least if you tried it in iWS or with your custom PSDK app?
Tried within custom app. In IWS should be this available, so the test in IWS can lead to the find out the root-cause or format in what the query should be.
Hi Guys,
I recently received a response from Genesys stating in iWS search functionality was only made available in 8.5 version of iWS. So if any of you have recently upgraded to this version and tested it please let me know. I am in the process of upgrading mine. I will post my results if at all iWS is doing what I am looking for.
Thanks in advance.
With Workspace desktop 8.5 latest, you can search ucs for any interaction and search attributes are configurable.
It is not limited anymore to my interactions or interactions assigned with contact.
It is possible to search for instance, any interaction assigned to agent xy or any interaction sent from address yz.
The attribute doesnt need to be searchable. But when it is not indexed, performance of such search can be low and results are coming slowly. This depends from number of records in ucs and current load.
Be careful when you will try to get real time result from attributes which are not searchable. Searchable attribute should be indexed by ucs. Nad results based on these atributes should come back faster.
Hi Robik,
Thanks for your response, but let me enlighten you here that even with iWS it doesn’t search using the StrAttribute columns instead searches for within the AllAttributes column and that is not a healthy way of doing it in a production environment since that column isn’t indexed.
So I am now on the mercy of Genesys to let us know if at all customer attribute indexing works with Apache.Lucene or not.
Appreciate your response, I will keep you guys posted, I have a call with the Genesys team next week.
Regards,
Upkar