Program Units in Designer

Designer for Module, Module Component and Item has the (last) branch Application Logic, which has sub-branches Events and Named Routines.

For the Events sub-branch, it is important to put the program code at the appropriate level - Module / Module Component / Item - because in the Forms module we get the Forms level trigger / block level trigger / item level trigger.

Unlike Events, it doesn't matter at what level in Designer we create Named Routines - they are always created as Program Units in the Forms module. So perhaps it makes the most sense to define Named Routines for Module.