Unity API - Programatically Validate Keywords before the Document Upload in Unity

[Mahesh_L]

Hi All,

I am trying to validate few of the keyword types which are already configured for a document type. I have started with validating a keyword with empty check.

But the script is not working as expected. The script is getting triggered while clicking the "Upload" button in Unity but the expected result is not arrived. Dont know what i am doing wrong. Please help me. Below is the script.

FileImportKeywordPanel keywordPanel = args.KeywordPanel;
KeywordType keywordType = app.Core.KeywordTypes.Find("Serial Number");
if(keywordType == null)
{
throw new Exception("Could not find serial number keyword type");
}
KeywordRecord keywordRecord = keywordPanel.KeywordRecords.Find(keywordType);
if(keywordRecord == null)
{
throw new Exception("Could not find serial number keyword type in keyword record");
}
try
{
Keyword keyword = keywordRecord.Keywords.Find(keywordType);
if ((keyword == null) || (keyword.IsBlank))
{
MessageBox.Show("Please fill the Serial Number", "Validation", buttons);
args.ScriptResult = DocumentFileImportPreArchiveScriptResult.Cancel;
return;
}
}
catch(UnityAPIException unityEx)
{
app.Diagnostics.Write(unityEx.ToString());
}

With Regards

LMK

[Chris_Tucker]

You can check if a date keyword has a value after the current date by using: DateTime.Compare(keyword.DateTimeValue, DateTime.Now) > 0. The DateTimeValue property will throw an exception if the keyword is blank or if it's not configured as a Date or DateTime keyword, so make sure that you check that before performing the comparison.

[Mahesh_L]

Thanks Chris. I could able to achieve what i wanted. Thanks a lot for your timely help. This is working fine in OnBase15 not in OnBase13. Is this expected behaviour?.

[Chris_Tucker]

The File Import - Pre Archive script was added in OnBase 14, so it won't work in versions prior to that. If you need this functionality in OnBase 13, your best bets would probably be to write a VBScript (which only execute in the thick client), route the documents through a scan queue and use a Post Index script for validation, or use Workflow to perform the validation.
Hope this helps!