I have mostly completed the work. I still have to add code to handle exceptions and do some extensive testing.

Using the web app, one can now attach a PDI transformation to a project. The app will analyze if a rule engine step is in the transformation. In case there are multiple rule engine steps, the user can select which one to use.

Now, when the user writes rules or actions, he/she no longer needs to type in the field names and the field types manually but the fields are selectable from a dropdown. This is easier for the user and avoids typos or wrong field type selections.

And there are some minor features that I want to implement. E.g. a check that is run before exporting the project file if all rules are consistant.

The code, database schema and a war file is available on http://github/uwegeercken

Recently I have begun to add logic to the web app, so that one can attach a PDI Transformation to a project. This way, the user does not have to type in the field names available and also the type of field (String, Integer, etc) does not need to be specified manually.

The task turned out to be more complicated than I had thought. The major problem is, that the web server running the Business Rule Maintenance Tool will need to contain the plugins that are used by the transformation. Otherwise the list of field names that are used by the rule engine step can not be retrieved - an exception is thrown.

Other than this, I have progressed well. The user will upload a transformation to the web server and it will find the list of fields available for the rule engine step. I still need to work a little bit on the workflow inside the web app and enhance and implement the error handling.