New Extended Log Message Action

[bgregory]

I have a suggestion for a new Log Message Action.

Currently if you have a scenario where there may be multiple return codes from an Action, you would have
to code them with separate Log Message Action statements, example below:

2024-08-04_13-25-54.jpg (118.25 KiB) Viewed 25148 times

Using my suggestion below, or one similar, you would only have to code one Log Message Action.
Or what might be a simpler implementation, being able to specify the Message Type using a variable,
then that variable could be used in the Log Message Action. Just some ideas. . .

2024-08-04_12-36-39.jpg (112.1 KiB) Viewed 25148 times

[Lana_K]

I would generalize your idea into adding a switch flow control (to replace multiple elseif's) with Action and Parameter instead of your Message Type and Message Text. Then it could be used for various scenarios, not just for messages.

[Oleg]

would generalize your idea into adding a switch flow control...

Executing or assigning variables by condition can be applied to almost any action. This will make action parameters and the action editor incredibly complex. It may also lead to loss of compatibility with older versions of tasks.
Let each action perform only the functions for which it is intended.