Workplace Search Connector Technical Preview feedback

[yakhinvadim]

Thank you for using the Workplace Search connector for Search UI.

While the connector is in Technical Preview, we would appreciate feedback, suggestions, and bug reports.

Please use this issue to report any of the above.

[lommaj]

I have a situation where we want to use the salesforce connector from workplace search - however I simply want to use salesforce data in our app - not workplace search + OAuth flow.

Will this work? Can I just get salesforce data via the typical app search API?

[JasonStoltz]

I don't know the answer off of the top of my head, but I am asking around to see if that's possible.

[lommaj]

thanks - this is a extremely common use case for salesforce data - and there are similar connectors for databases like postgres, since having your web app hit salesforce directly is not an ideal pattern.

[lommaj]

Even if it means not using the UI connector directly to the database - and just implementing the same interface on a server to handle communication between front end UI and backend search..

So headless app search UI connector <-> API implementing the same interface expected <-> elastic salesforce connector data

[lommaj]

just to follow up here - it does work as expected however...

there is no way join objects from the salesforce connector - so its basically moot for us.

[JasonStoltz]

What version are you on? I know if in 8.4 and/or the upcoming 8.5 release we've been moving to make the data ingested by a connector decoupled from the Workplace Search product itself.

[JasonStoltz]

Check these docs out, they may explain how to accomplish what you're aiming to do: https://www.elastic.co/guide/en/enterprise-search/current/engines.html#engines-create-from-content-source

[danajuratoni]

cc: @serenachou

[lommaj]

We actually just wanted to use your pre-built sync to grab data from our salesforce org to use on our public website.

We ended up just building a task to query and push it to the database ourselves. It seemed like we could configure the salesforce connector to grab objects but could not setup foreign key relationships on them.

[serenachou]

Hmm interesting @lommaj Would you be interested in sharing more details on the solution you ended up using, did you build the task in a specific language? Where do you host the logic that syncs?

[lommaj]

sure - we have a backend that runs on nestjs and you can bootstrap parts of that application on a lambda to do a task.

so we have crons that run in AWS to trigger that every few minutes.

we also have a salesforce change data queue that goes to AWS SQS and some things we process in real time using that queue.

so in these cases - we have a service we wrote in typescript to grab the objects we need and normalize for elastic. Which is nice because the salesforce connector only synced once ever 2 hours and we can do this more often.

[blackge]

Hi,

We are implementing Workplace search in our app using Search-ui and are having a problem with private sources. Currently if we use the workplace search UI to search, we get Slack messages returned. These are not appearing through the workplace search integration in search-ui. Is that a bug or expected behaviour?

[chriscressman]

private sources ... These are not appearing through the workplace search integration in search-ui. Is that a bug or expected behaviour?

Hi @blackge. Unfortunately, this is the expected behavior. Private sources are not implemented in the search API for Workplace Search, so Search UI does not receive results from those sources.

Searching private sources is available through the default search application only.

[blackge]

Thanks @chriscressman. Do you have any plans to integrate this in the future?

[chriscressman]

@blackge No, that change isn't currently on the roadmap. cc @serenachou