Update! The Java Object Model support added as a beta feature in Decision Modeler 2.1 has been improved and officially launched in Decision Modeler 2.2. You can manage and import Java classes directly in Decision Modeler, no need to go through a Blaze Advisor project upload anymore.
Not only can you bring in Java classes as part of your business object model, but you can also use a Java class to define the entry point signature in your setup configuration. Now when you import a .jar file and use one of the Java classes, you see messages to help you manage dependencies in situations where you may need to modify your .jar file contents.
Comment here with any questions. Get the latest trial version of Decision Modeler and see how easy it is to author decision logic.