Hi Enrique,
That is my understanding. If the class does not show up in the logging.jsp page as a drop down, I have directly added the class to the edit box and submitted.
I was able to then see that class reported in the J2EE logs.
The challenge I have found it how to ensure that "noise" is limited, to avoid overwhelming the administrator to debug.
One answer, was to directly update the log4j properties file with another "appender", and have ONLY select loggers go to that file.
I have one just for im.feeder, ims.policyxpress, ims.tasktrack.custom to allow a capture of the business flow.
I would like to update this process to have all the PX rules (currently in use) to create a screen LAH with a unique GUID and pass that GUID from event to event.
Only three (3) ways I have found to persist this data was to store it temporary
1) on the user profile (a I/O hit) or
2) file (an I/O hit) or
3) use the IME's Advanced Settings › Miscellaneous > User Defined Properties {this will be available to the entire IME, but use it for one-id-and-one-use-case at a time}
However, since the attempt to capture business logic, the above methods do assist.
Cheers,
A.