I don't have any quick way to convert from data-transform to an activity, although you could probably click the coffee cup and then copy-paste relevant pieces of the java into java steps of a new activity.
If you ended up pasting a huge piece of the java into one large java step of an activity, here's a useful call you can use for helping to debug that java:
pega_rules_utilities.sendDebugMessageToTracer("The current value of xyz is " + xyz,"Pega-ProCom");
In order to make this show up in tracer, add event type "Debug" to your tracer settings screen, plus make sure you have enabled "Pega-ProCom" ruleset at the bottom of the window.
Can you please say a bit more about the particular transform you’re trying to debug ? Is it particularly long in number of steps and you’re trying to figure out which step is running into a problem ? Or is it deeply nested ? Knowing the particular sort of problem you’re having with the transform may help give some ideas for how to debug it. /Eric