Hello Ronaldo,
"determinations" are intended to be used to handle side effects. They do not offer any parameters that allows consumers to hand over details. If you would like to execute logic immediately as soon as a user clicks on a menu option, an "action" would be more suitable. There are different ways of modeling:
- If you have multiple actions however based on the same implementing class, you can inside switch between different implementations by the help of IS_CTX-ACT_KEY importing parameter.
- Or of course you can have one single implementing class for each action as this is the standard way of modeling actions.
- Finally you might create an action importing parameter to allow the consumer to hand over some kind "function code" that is evaluated inside of your code via IS_PARAMETERS.
If you however have a real side effect and thus you would like to keep the determination, you might need some kind of customizing that can be evaluated in your determination and that is maintained upfront by the consumer.
Best regards
Tilmann