The purpose of this article is to show how easy it is to use the https://www.microfocus.com/documentation/idol/IDOL_24_1/Content_24.1_Documentation/Help/Content/Actions/Query/Query.htm Query functionality of IDOL. In this example we integrated the search criteria to be the highlighted text in Outlook.

We start with our VS Project to create our Outlook Add-In

There are many other resources available on how to make an Outlook Add-In.

In order to bring up the menu on highlighted text in Outlook with a right hand mouse button click, the context menu is called

<contextMenu idMso="ContextMenuReadOnlyMailText">

and the selected text is called "ThisAddIn.Application.ActiveExplorer.PreviewPane.WordEditor.Application.Selection.Text"

Once we have the two we can query idol as follows across all databases and by restricting the returned characters to make the return value more predictable. We also added term highlighting as well.

http://idolserver:9100/action=Query&DatabaseMatch=*&MaxPrintChars=250&Highlight=terms&Text=" + SelText ( Our text selection )

When to do a query to IDOL similar to the one above we get a reply similar to the one below and we need to parse out what we want to make our clickable links.

In order to create our clickable links we used our WebView2 Control and add that into a CustomTaskPane Control for Outlook.

Then its a matter of building the html from the XML and viewing in the form.

The results are like the following. Our highlighted term is AGILUM …Rev21 and we can see that IDOL found exactly what we wanted and shows the matched terms highlighted in red.

See the IDOL_Search CustomTaskPane displaying the search results.

Then the image below shows the results from clicking on one of the result links.

I hope you can find new ways to incorporate IDOL into your environment.

Many thanks

Phil ****

Looking at our source documents in our HR Directory with Extended ECM, everything looks fine. However one of these documents has been incorrectly named with an incorrect HR Number as part of it's metadata. IDOL will help us to discover this error and make any corrections before we transfer our content to our target, in this example to Core Content.

The first step is to bring the files locally and add the required metadata into a small DB.

We can see below the table and we added the original NodeID so this could be referenced from the new target system.

Now comes IDOL which will use Eduction to find any occurrence of HR-XX in these documents. Once found new Entities will be added to the FlowFile and we will extract those values and put them into a different table in the same database.

We can see that the Employee Code of Conduct file which is called HR-34 Policy - Employee Code of Conduct is incorrectly named as INSIDE the document it's described as HR-29. Now we have the chance to amend the file name to the correct one which will be HR-29 - Policy Employee Code of Conduct and send to our target of Core Content.

Our IDOL Flow looks like the following..

Here we make the corrections and save before running our upload into Core Content.

Here is the result and we see that in fact the HR-34 was incorrectly named and now we have correctly named and applied the correct metadata.

I hope this serves as an introduction into just some of the capabilities of IDOL.

#GoBeyond Always Be Learning

Phil ****