We are testing the Docusign integration with OnBase and have come across a weird exception error. Users receive an exception error whenever they try to perform an action on a document after it's been sent to docusign. The full error is as follows:
Hyland.Common.Core.Keywords.Exceptions.InvalidKeywordValueException: An Error occurred while parsing a keyword value for Keyword Type 'Null Keytype' (0), check the inner exception for details. ---> System.InvalidOperationException: Value length of 36 is greater than 20 for Keyword Type 'Null Keytype' (0).
at Hyland.Common.Core.CommonCoreGuard.ThrowOptionalInvalidOperationException(String message, FailureOptions options)
at Hyland.Core.KeywordValueNumeric`1.parseLocalizedString(String value, FailureOptions options)
at Hyland.Core.KeywordValue`1.TrySetLocalizedValue(String value, FailureOptions options)
--- End of inner exception stack trace ---
at Hyland.Core.KeywordValue`1.TrySetLocalizedValue(String value, FailureOptions options)
at Hyland.Core.DocuSignJob.ArchiveEnvelopePDF(DocumentGeneric envelopePDF, Int64 itemtypenum, Int64 keytypenum, String envelopeID, Int64& itemnum)
at Hyland.Core.DocuSignJob.AttemptDownload()
at Hyland.Core.DocuSignJob.GetHistoryToken(Int64 docID)
at Hyland.Core.HostedSigning.Services.DocuSignServices.GetHistoryToken()
Keyword Type 'Null Keytype' is not a kw we use, let alone on this doctype we're testing. Nor do we have the ability to alter since it is a core system keyword. I'm not sure where it's getting this value of 36. Diagnostic Console doesn't elaborate more on this error either. If I had to guess, the 36 value may be the Envelope ID? I'm not sure but if anyone has any experience with this issue or ideas on how to resolve it I'd greatly appreciate it.
1 ACCEPTED ANSWER
I think it may be trying to set the envelope ID or Template ID as a keyword, but the keyword type maybe was never defined properly in OnBase config.
open onbase config and go to Document > Hosted Signing > DocuSign and check the advanced settings. if either one of these are enabled and show a null keytype like this, you will need to set the appropriate keyword or disable the feature.
If that isn't the problem you can open a support ticket so we can troubleshoot it.
