on 02-09-2016 7:49 AM
I would say that editing scripts in your QA system is probably the wrong thing to do. If there are changes required, to either scripts or the screen, you should make those changes in your development system and re-transport, just like you do with ABAP developments. Just because it is quick and easy to fix scripts in QA (and try to replicate those fixes correctly in DEV afterwards, obviously) doesn't mean that's the right thing to do.
That said, without the setting provided in the note Tamas mentions, debugging scripts is pretty difficult - there's no way to add "debugger" statements to the scripts to trigger the browser debugger at an appropriate point. It would be nice if there was a way to do this without also allowing script changes, but right now there isn't.
In summary, you can do it (now) but be careful
Steve.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In SP02 there is a note to handle this: 2273808
I'm not aware of an equivalent for SP01.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.