Currently when adding a field to a table/task or linking a task to a table, the default logic is that the field is added as a input parameter in default/layout/context procedures. As a developer it is possible to disable this, which specially in the case of tab-tasks could lead to performance gain when the task is executed for multiple rows and there is a context procedure for the table that doesn’t do anything with the task.
When developing in the SF, you often make small changes that you want to see/test immediately. And when it doesn’t involve any data model changes, you don’t want to wait for the full creation process to finish. However the default/layout/context easily break when a parameter is added, forcing the developer to regenerate each of them again manually.
To improve these two points, it would be better if the software factory would automatically detect which parameters are actually being used in the program object and just comment the unused parameters out (leave them commented so a developer could still easily see which parameters are available).
The settings under ‘Use concept’ could still be used if there ever is a need for a developer to force it, the options could then be changed to: Automatic (default), on, off.
This would improve performance of applications and reduce actions a developer needs to take:
🚀 Ideas to be 10X faster - which SF workaround to eliminate? | Thinkwise Community
