validation script for multiple document classes

Question

We are working on a validation script and know how to set things up. Currently we create validation scripts based on each customer. Of course we have to ensure that each batch/document uses the same fields but is there a way to decouple the script from a specific document class?

Then it would be possible to create an external script (with a Git flow) and roll it out for multiple customers. Currently we can only create one unique script per document class.

Just to clarify, are we talking plain KC, or Kofax Transformations? — Wolfgang Radl, Oct 22 '19 at 19:56

score 0 · Accepted Answer · answered Oct 23 '19 at 12:31

0

One way to decouple validation scripts from specific classes are field scripts. There's a drawback, though - field scripts are tied to one specific field; you can't access any other runtime elements (such as index or batch fields) via the API. There are some tricks to work around that, but as said - by default, it isn't possible.

I recommend creating a standalone function library and then reference it from your field or validation script. While this requires you to roll out said DLL to any station running Index.exe, this approach makes your DevOps life easier.

answered Oct 23 '19 at 12:31

Wolfgang Radl

2,319
2
17
22

so you would recommend creating a big library solving all my problems and for each station I just pass in the required fields? – Oct 23 '19 at 12:34
1

Doing so certainly makes many aspects easier - this includes functional testing, source control, and reusability. The obvious drawback is rolling out that library to each client, but KC offers a deployment utility (never used it myself though). – Wolfgang Radl Oct 23 '19 at 15:45

validation script for multiple document classes

1 Answers1