Other languages are under development — if you don’t see yours, call!. We also have tools that let us work with the HTML produced by almost any application that runs in a browser window. Additional tools allow us to handle IDEAL, Datacomm, and some other legacy mainframe environments. New languages take a matter of weeks to support. But, we don’t always need to do reverse-engineering, sometimes we can redevelop a legacy application by capturing the screens and reports, or even by working with a user guide.
A second alternative is for us to implement flexible business rules code that can be applied during forms processing. For example, we have reusable business rules code that we developed for a very complex survey project. That’s not an engine, though. Not really. But, it serves well for some applications.
Third, we are also able to integrate a rules engine with our reusable code. We did that at Freddie Mac and demonstrated it within the context of loan underwriting — and those rules are VERY complex. We’ve worked with I-Log and Jess and a couple of others, so we know how to do it. But, before plunging down this path, we recommend that you pilot the approach and verify that the functionality and performance of your selected business rules engine will meet your needs — and your pocketbook.