We’ve been looking at the prospect of purchasing the AyaNova system for our company system. We love everything about it but are having difficulties getting the Wiki search to search through the PDF, MSWord, etc. files as well as the data in the main system. Other systems we have looked at do this very well but lack a lot of the user interface to the business part of the system. Are there any topics or suggestions? Right now, that is the only stumbling block for us – a robust knowledgebase system is a requirement for our new system.
The Search Database feature of AyaNova can search for data entered into AyaNova entry screen fields - i.e. all text fields of an AyaNova workorder entry screen, of an AyaNova Part entry screen, all text in a Wiki page, etc.
But sorry, no, an uploaded file such as a PDF or Word document to a Wiki object is not searchable via the Search Database feature as the files textis not entered in searchable fields in AyaNova - the file itself is saved within the AyaNova database in that format and not readable nor indexed for searching by the Search Database.
If instead the PDF or Word document’s contents were copied into the Wiki itself page itself, than yes,the textwould thanbe searchable, as the Wiki page’s textis indexed and searchable by the Search Database feature.
I have put this onto the list for development to look into for a future version of AyaNova as would need to be specifically developed for as it would require inclusion of specific controls that can read the PDF file, the Word document etc so that its words can be indexed for searching etc. But its now something that development will look into. Thank you for your post, as it has provided a great suggestion for a future feature for AyaNova.
That is what we suspected. Does the SDK/API allow us to develop/link our own search engine or atleast create a new button in the AyaNova Application to access our file search? I’m thinking at the very minimum, we could use the built-in Windows file manager search system. I also understand there are numerous “google-ish” shared search engines available.
Also looking at creating templates for the wiki pages. Haven’t done a lot of research but still looking. I also found that adding a link to a customer asset (unit) creates a funny link in the document – it puts a lot of the characters from the record with the link.
That is what we suspected. Does the SDK/API allow us to develop/link our own search engine or atleast create a new button in the AyaNova Application to access our file search? I’m thinking at the very minimum, we could use the built-in Windows file manager search system. I also understand there are numerous “google-ish” shared search engines available.
Also looking at creating templates for the wiki pages. Haven’t done a lot of research but still looking. I also found that adding a link to a customer asset (unit) creates a funny link in the document – it puts a lot of the characters from the record with the link.
Thanks
Tim
Hi Tim, yes, the API can be used to create a plugin for AyaNova that is accessed from the plugin menu option within AyaNova. There is a sample plugin with source code available see the Development forum here: http://forum.ayanova.com/Forum101-1.aspxand specifically the pinned topic “Getting started…”. With a plugin you have access to every feature within AyaNova as well as anything else you want to cook up through program code. (Note that we will very likely add indexing of attached documents in a future release as it’s an excellent suggestion.)
If you have any development questions feel free to post them there, that’s my usual hangout as I’m one of the developers for AyaNova.
Note that AyaNova already comes with an includedXTools plugin which you can customize to point to an externalexecutable of your choice accessible from within AyaNovawithout writing any code if you have an existing search application.
As for the AyaNova hyperlinks within wiki pages, it only shows funny characters in the editing form. Thosecharacters arean “AyaNova:” hyperlink with the object type id number followed by a comma and then the specific Guid id number of the object in question, however, when viewing the wiki page in the viewing form(what you see when you first open a wiki page)AyaNova automatically substitutes a nicely formatted human readable link when it comes across AyaNova: style hyperlinks.
Insert a link, save the wiki page then open it to view and you’ll see what I mean.