As with the other facilities of SQL Developer, you can opt to view the relevant SQL for this change.
All Oracle is really doing here is calling the relevant API, but what I also noticed the first time I used it was the autonomous transaction pragma it applied to the anonymous block.
declare PRAGMA AUTONOMOUS_TRANSACTION; begin wwv_flow_api.set_security_group_id(p_security_group_id=>100001); wwv_flow_api.set_application_alias (p_flow_id=>101,p_alias=>'TIM_0101_b'); commit; end; /In the past I've quite happily applied this pragma for a procedure defined within a package, but this demonstrates we can also define independent transactions within these anonymous PL/SQL blocks, in addition to certain triggers.
Something I added to the memory bank when I first stumbled on it.
A final note - you can also kinda "name" your anonymous block to assist your documentation process, ie - there is no reason why you can't finish with: