Use a checkin filter such as validateStandard.
In my custom Java class I try to implement 'FilterImplementor' and I get a type reference warning saying JDeveloper can't find the type 'FilterImplementor'. I tried importing intradoc.shared.FilterImplementor, and that is not working either. Anyone have any ideas for me to get this resolved.
Did you add the Intradoc JAR or Intradoc classes to your build path?
Again, very helpful, Jonathan. Thanks. If I deploy this custom Java class to other JVMs, do I need to make sure that Intradoc JAR goes aong with it? Also can I create a custom /lib folder in my project, move that Intradoc JAR into it, refactore the jar reference in my project, and deploy it that way?
You would only use the Intradoc classes if running as a service, service handler, filter or class alias as a component within WebCenter Content. In this case, since it is running inside WebCenter Content, you do not need to bundle the Intradoc classes since they are already on the classpath.
If you are trying to code something that will not run inside WebCenter Content, you want to use RIDC: http://jonathanhult.com/blog/2012/12/ridc-examples/
Yep, I initially looked at RIDC and was writing to WCC/DAM using it, but opted to go your route (filter and a criteria workflow that will call my custom class on check-in) since it's out of the box, and our digital librarian(s) will be working in WCC and it is pointless to have them use a custom UI wired up to RIDC and the UI in WCC.
Thanks again for the helpful info. I really appreciate it.
You would control this logic within your FilterImplementor code.
You would retrieve values for metadata fields and if they meet the criteria, continue with your custom logic. Otherwise, return and do not do anything.