Page Comparison

...

1. In a SQL database, create a View that extracts the data for each of the keywords.  In this example, the view was created in the Colleague ODS database because the keyword data lies in Colleague.  
2. Create a SELECT statement that runs the view.
3. Create a Powershell script that runs the SELECT statement from #2 above.  In this instance, Les created this script on his C: drive.  This script will create a text file that gets imported into OnBase
4. Make sure that all of the keywords for your AFKWS exist.  If they don't exist, create them in OnBase config.
5. Create a new AutoFill Keyword Set in OnBase config.  Make sure that the order of your keywords in the AFKWS match the order of the data in your text file.
6. Go to the document type that needs the AFKWS and find the primary keyword.  Make sure that this primary keyword is at the top of the list of keywords.  Add any new keywords that you've created.  There's a place to indicate an AutoFill Keyword Set.  Choose your new AWKWS from the list in the drop-down.
7. From the machine with the text file (Les' in this case), go into OnBase config and choose the Import menu.  
8. Choose AutoFill Keyword Processor.  Create a new processor for your new AFKWS.
   
9. Go to OnBase client and Re-launch.  
10. Go to the Admin menu and choose AutoFill Keyword Processor.  Find your new AFKWS, right-click, and execute.  This will bring in the new keywords.

 Do lookups on existing AFKWS tables

There was an office at Carleton that wanted to create a correspondence document.  It has a Sender ID, Recipient ID, and a Referenced ID on it.  We wanted names to go with those IDs as well, but didn't want to type them.  All of these people are in the Advance People AFKWS that is updated each night.  So here's what I did:

1. Create the new keywords
2. Create the AFKWSs
3. Make them external AFKWS.  Look at the SQL code on PRES Sender AFKWS.  The user must have the ODBC of OnBase-production, which is the DSN.  The user ID is hsi, with the hsi password.  Make sure that the SELECT statement columns line up with the keywords on the AFKWS.
4. Attach the AFKWS to each of the ID keywords
5. Put them all on the document - which has no assigned AFKWS.  If there's an AFKWS on the document, it will negate the AFKWS on the keywords themselves.
6. Re-launch the client, enter the primary key, hit tab, and the secondary keys will fill in.

You can have as many of these AFKWS on the document as you'd like, as long as they are assigned to the keywords.  If there's an AFKWS assigned to the document, it will override the AFKWS on the keywords.  Further, if you put AFKWS on the keywords, it will apply to ALL documents that use these keywords, so keep that in mind.