In the SF you can create a subroutine procedure to create a non-gui task. However, you can also create a task and not create a table task for it. I was wondering in what situation one would use a subroutine procedure over a task without a table task?
When using subroutines there are some disadvantages. There are 2 places you need to maintain the logic (in tasks and in subroutines). Functionality can not be shared between tasks and subroutines. Subroutines can not be added to the gui or a process flow. This sometimes leads to new placeholder tasks to give the subroutine some GUI functionality.
So therefore i'm wondering what is the added value of the subroutine procedure?
Best answer by Vincent Doppenberg
View original