Refer to SILK PERFORMER | SETTINGS | ACTIVE PROFILE | SIMULATION | ERRORS | ADD.
Within the Drop Down menu, choose BrowserEngine for MODULE. Here you will find all BrowserEngine codes, as well as their default severity settings, i.e. codes defined as errors, warnings etc.
Am I looking in the right area? According to information Jonny gave me, a BE: 65 error should be a severity of "TRANS_EXIT". However in Silk Performer 17.5, all I see it as is "error".
I'm hoping to modify an error handling library I wrote with Jonny's assistance to capture both BE: 8 and BE: 15 errors. Would this be handled like this?
handler Handler0 <EVENT_RAISE_ERROR>